Re: X-Windows errors

[Philippe Roussel]

Le samedi 25 octobre 2008 à 17:24 +0200, Fred Kiefer a écrit :

> If this wasn't the source of the problem then we need to dig deeper. The
> first thing to do is to run the application with a debugger attached and
> set a break point into XGErrorHandler and report the backtraces you get
> from it. That will help us to pin down, which operations are causing the
> messages.

I got this one under gdb

Breakpoint 2, XGErrorHandler (display=0x882b418, err=0xbf921728) at 
XGServerEvent.m:127
(gdb) bt
#0  XGErrorHandler (display=0x882b418, err=0xbf921728) at XGServerEvent.m:127
#1  0xb6bf2ef9 in _XError () from /usr/lib/libX11.so.6
#2  0xb6bfafe8 in ?? () from /usr/lib/libX11.so.6
#3  0xb6bfb39a in _XReply () from /usr/lib/libX11.so.6
#4  0xb6bee667 in XSync () from /usr/lib/libX11.so.6
#5  0xb6bee805 in ?? () from /usr/lib/libX11.so.6
#6  0xb6bfb7c2 in ?? () from /usr/lib/libX11.so.6
#7  0xb6b4acc2 in XShmCreatePixmap () from /usr/lib/libXext.so.6
#8  0xb6e007ac in +[XWindowBuffer windowBufferForWindow:depthInfo:] 
(self=0xb6e27ea0, _cmd=0xb6e2bef0, awindow=0x8951128, aDI=0xbf92199c) at 
XWindowBuffer.m:343
#9  0xb6e0b42e in -[XGCairoXImageSurface initWithDevice:] (self=0x895a068, 
_cmd=0xb6e2b4c0, device=0x8951128) at XGCairoXImageSurface.m:57
#10 0xb6e09b94 in -[CairoContext(Ops) GSSetDevice:::] (self=0x895a0e0, 
_cmd=0xb6e26a18, device=0x8951128, x=0, y=64) at CairoContext.m:136
#11 0xb6df7131 in -[XGServer(WindowOps) setWindowdevice:forContext:] 
(self=0x8829db8, _cmd=0xb6e1c648, win=1, ctxt=0x895a0e0) at 
/opt/GNUstep/System/Library/Headers/AppKit/DPSOperators.h:1141
#12 0xb6dd44ee in -[GSContext initWithContextInfo:] () at GSContext.m:204
#13 0xb7ce4aa9 in -[NSWindow _startBackendWindow] (self=0x894cf18, 
_cmd=0xb7e732f0) at NSWindow.m:825
#14 0xb7ce4e02 in -[NSWindow _initBackendWindow] (self=0x894cf18, 
_cmd=0xb7e73398) at NSWindow.m:871
#15 0xb7ce5853 in -[NSWindow 
initWithContentRect:styleMask:backing:defer:screen:] (self=0x894cf18, 
_cmd=0xb7ddccd0, contentRect={origin = {x = 0, y = 0}, size = {width = 64, 
height = 64}}, aStyle=64, bufferingType=NSBackingStoreRetained, flag=0 '\000', 
aScreen=0x88b1918) at NSWindow.m:1038
#16 0xb7b68e2c in -[NSApplication(Private) _appIconInit] (self=0x8819710, 
_cmd=0xb7ddc6f0) at NSApplication.m:3536
#17 0xb7b60c1d in -[NSApplication finishLaunching] (self=0x8819710, 
_cmd=0xb7ddc868) at NSApplication.m:947
#18 0xb7b629e9 in -[NSApplication run] (self=0x8819710, _cmd=0xb7dd2000) at 
NSApplication.m:1374
#19 0xb7b44cdd in NSApplicationMain (argc=2, argv=0xbf921e84) at Functions.m:74
#20 0x0806febe in main (argc=1457883477, argv=0x30ec8353) at SimpleAgenda.m:30

Unfortunately when I try to continue to get another backtrace the
application receives a SIGABRT. Do you know how to get around this
problem ? 

I just tried with another application to be sure SimpleAgenda is not the
cause and Gorm gives me the same kind of logs.

Philippe