Custom Query (74 matches)

While translating the manual, I just installed the latest 2.91rc1 from the dev list on a fresh AOS 5 to test the Spanish resources in a live environment, and try to keep UI and docs well in synch.

I quickly found out that both buttons 'Save' and 'Cancel' at the bottom of the Properties notebook do nothing and the same thing -- I tried a few settings (filters, and display properties of the tb, pmwp hints) and they all seem to be saved right away, which in turn renders both buttons useless.

This is new with XWP 1.0.12. It happens after you open a second group member with Xcenter open. Generally after you reopen Xcenter it is fine until you open another group member. Sometimes you get a very small menu (clipped or no text) instead of the trap.

ArcaOS Desktop trap message -- Date: 2018-12-01, Time: 16:22:39
-----------------------------------------------------------

An internal error occurred in ArcaOS Desktop (XFLDR.DLL).
Please send a bug report to xworkplace-user@netlabs.org
so that this error may be fixed for future ArcaOS Desktop versions.
Please supply this file (?:\xwptrap.log) with your e-mail
and describe as exactly as possible the conditions under which
the error occurred.

Running XFLDR.DLL version: 1.0.12 built Nov 24 2018
Running OS/2 version: 20.45.0 (WSeB kernel)

excHandlerLoud:
    Exception type: C0000005
    Address:        1C4846FC
    Params:         00000001  00E50000  
XCPT_ACCESS_VIOLATION: XCPT_READ_ACCESS -- Invalid read access from 0x0053:00E50000.
Explanation: An attempt was made to access a memory object which does
             not belong to the current process. Most probable causes
             for this are that an invalid pointer was used, there was
             confusion with administering memory or error conditions 
             were not properly checked for.

Process information:
    Process ID:      0x2D
    Process module:  0x493 (J:\OS2\PMSHELL.EXE)
    Trapping module: 0x1D40 (J:\SYS\APPS\XWPS\PLUGINS\XCENTER\LSWIDGET.DLL)
    Object: 1

Trapping thread information:
    Thread ID:       0x8 (8)
    Thread slot ID:  0x77 (119)
    Priority:        0x31F

Exception handler:
    Set by:          D:\prj\xwp\new\xworkplace-1-0\src\xcenter\ctr_engine.c::ctrp_fntXCenter()

Thread identification:
    TID 0x8 (8)  (XCenter)
The following threads could be identified:
    PMSHELL Workplace thread ID: 0x1
    NotifySentinel: ID 0xB (11)
    RefreshFindFolder: ID 0xC (12)
    RefreshNotificationPump: ID 0xD (13)
    NotifyServer: ID 0xE (14)
    Party: ID 0xF (15)
    Worker: ID 0x10 (16)
    Bush: ID 0x11 (17)
    Wimp: ID 0x12 (18)
    File: ID 0x13 (19)
    LazyIcons: ID 0x1E (30)
    XCenter: ID 0x8 (8)
    PulseWidgetCollect: ID 0x20 (32)

Global lock semaphore is currently not owned.

Registers:
    DS  = 00000053  
    ES  = 00000053  
    FS  = 0000150B  
    GS  = 00000000  
    EAX = 00000000  not an address
    EBX = 00018005  valid, flags: read execute 
    ECX = FFFFFFFF  invalid address
    EDX = 1B79FFFF  valid, flags: read write committed shared 
    ESI = 00E76330  valid, flags: read write committed 
    EDI = 00E50000  valid, flags: read write 

Instruction pointer (where exception occurred):
    CS:EIP = 005B:1C4846FC  valid, flags: read execute committed shared 
    EFLAGS = 00210246

Stack:
    Base:         00E30000
    Limit:        00E77000
    SS:ESP = 0053:00E75B28  valid, flags: read write committed 
    EBP    =      00E75FDE  valid, flags: read write committed 

Stack frames:
              Address   Module   seg:ofs
    CS:EIP  : 1C4846FC  LSWIDGET 02:000046FC
                                 between ButtonWndProc + 0x1AD 
                                     and TskBarFrameWndProc - 0xE5C 

    00E75FDE: FFFF00E7  unknown  Error: DosQueryModFromEIP returned 487

    pulStackWord >= (PULONG)ptib->tib_pstacklimit

Ctrl+Esc causes is as does Alt/Ctrl?+Tab. Opening and closing XCenter fixes it even if the full screen session is still open. The shut down dialog disappears in some cases but if it doesn't and you skip XCenter shut down completes. After the failure Shutdown and restart desktop are greyed out. However if you restart the desktop from CADH you can then shut down.