Re: gtk build crashing

[Jan D.]

robert wrote:
> On Sat, 1 Mar 2003, address@hidden wrote:
>
>
> > > cvs update on 23rd Feb, I regularly get a crash (well an exit raher than
> > > a crash) with the message
> > >
> > > X protocol error: BadDrawable (invalid Pixmap or Window parameter) on
> > > protocol request 62 
> >
> > Try some of the techniques outlined in etc/DEBUG, heading
> > "** If you encounter X protocol errors".
> >
> > It is interesting to know if you get this error in sync mode.
>
>
> Jan,
>
> I get this error in sync mode with the following traceback
>
>  bt
> #0  x_error_quitter (display=0xbffd1474, error=0x405d9fa8) at xterm.c:12730
> #1  0x080bd169 in x_error_handler (display=0x84f60c0, error=0xbffd1474)
>     at xterm.c:12754
> #2  0x40545bf1 in _XError () from /usr/X11R6/lib/libX11.so.6
> #3  0x40544b0f in _XReply () from /usr/X11R6/lib/libX11.so.6
> #4  0x40540845 in XSync () from /usr/X11R6/lib/libX11.so.6
> #5  0x402a629c in gdk_flush () from /usr/lib/libgdk-x11-2.0.so.0
> #6  0x402986e8 in gdk_window_process_all_updates ()
>    from /usr/lib/libgdk-x11-2.0.so.0
> #7  0x40298731 in gdk_window_process_all_updates ()
>    from /usr/lib/libgdk-x11-2.0.so.0

...

Darn, sync in GTK does not really mean sync, it does its own buffering that 
can't be put into sync mode.  I've made one change that might have impact, can 
you try a newer CVS?  Also, does this only happen with GTK?

Thanks,

        Jan D.