Re: XPutImage to a destroyed window (should gdk use another error handler?)

On Mar 7, 2004, at 4:01 AM, Michal Maruška wrote:
#0  0x405251c2 in select () from /lib/
#1  0x40344b64 in __JCR_LIST__ () from /usr/X11R6/lib/
#2  0x402a0fa1 in _XFlushInt () from /usr/X11R6/lib/
#3  0x402a0ef5 in _XFlush () from /usr/X11R6/lib/
#4  0x4029b5d5 in XSetInputFocus () from /usr/X11R6/lib/
#5 0x0807049a in remove_window (w=0x82d4608, destroyed=0, from_error=0) at windows.c:300
#6  0x0805632f in error_handler (dpy=0x0, ev=0x0) at display.c:137

this is a bug - the error handler should never generate X requests. From looking at the original sawfish code I can't see how this would happen since remove_window is explicitly told whether or not it's being called from within the error handler,


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]