It took me some time to get even only a 'nice' stack trace for the
X error within ishmail. At first one had to figure out the X error handler
that gets installed, waiting for exit() didn't help here ...

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Resource id in failed request:  0x0
  Serial number of failed request:  88

Problem is "low-level" triggered by an early XtAppCreateShell ().
At least upon first glance the app is quite happy after neglecting the error

[...]
#1  0x40267449 in _XError () from /usr/X11R6/lib/libX11.so.6
#2  0x40265c16 in _XReply () from /usr/X11R6/lib/libX11.so.6
#3  0x40261431 in XSync () from /usr/X11R6/lib/libX11.so.6
#4  0x402614bb in _XSyncFunction () from /usr/X11R6/lib/libX11.so.6
#5  0x40248454 in XChangeProperty () from /usr/X11R6/lib/libX11.so.6
#6  0x401fb314 in RealizeWidget () from /usr/X11R6/lib/libXt.so.6
#7  0x401fb464 in XtRealizeWidget () from /usr/X11R6/lib/libXt.so.6
#8  0x401fe198 in ManageChildren () from /usr/X11R6/lib/libXt.so.6
#9  0x401fe30e in XtManageChildren () from /usr/X11R6/lib/libXt.so.6
#10 0x401fe3fb in XtManageChild () from /usr/X11R6/lib/libXt.so.6
#11 0x401f06e8 in XtCreateManagedWidget () from /usr/X11R6/lib/libXt.so.6
#12 0x400d0056 in XmGetXmScreen (scr=0x831cbe8) at Screen.c:935
#13 0x4012fc4e in LTGetDesktopLogicalParentForShell (w=0x8388b88) at Vendor.c:898
#14 0x4012fd0f in secondary_object_create (req=0xbfffe754, new_w=0x8388b88, 
args=0x8384728, 
    num_args=0xbfffe50c) at Vendor.c:928
#15 0x4012ffe5 in initialize_prehook (req=0xbfffe754, new_w=0x8388b88, args=0x8384728, 
    num_args=0xbfffe50c) at Vendor.c:995
#16 0x4003ec05 in InitializeRootWrapper (request=0xbfffe754, new_w=0x8388b88, 
args=0x8384728, 
    num_args=0xbfffe50c) at BaseClass.c:1523
#17 0x401efbb5 in CallInitialize () from /usr/X11R6/lib/libXt.so.6
[dto ...]
#26 0x401efb7d in CallInitialize () from /usr/X11R6/lib/libXt.so.6
#27 0x401f00d2 in xtCreate () from /usr/X11R6/lib/libXt.so.6
#28 0x401f0966 in _XtAppCreateShell () from /usr/X11R6/lib/libXt.so.6
#29 0x401f09d4 in XtAppCreateShell () from /usr/X11R6/lib/libXt.so.6
#30 0x817a87f in HalAppC::HalAppC (this=0x8317910, argc=0xbffff470, argv=0xbffff480, 
    _name=0x8272646 "ishmail", clss=0x827263e "Ishmail", fallbackResources=0x0, 
options=0x0, 
    numoptions=0) at HalAppC.C:347
[...]


As written earlier(?) debugging here is no fun, since on linux i86 and alpha gdb like 
to crash while debugging, and especially on alpha gdb tends to produce nonsense output 
...
Also it's hard to 'follow' a C++ app through gdb. I tried even gdb 5.0 is there
something better than 's' to really go step by step (following all
constructors's calls, etc.)?

-- 
Alexander Mai
[EMAIL PROTECTED]

Reply via email to