* Daniel Stone wrote: > Hi, > > On Fri, Jul 08, 2011 at 12:51:19PM +0200, Thierry Reding wrote: > > * Thierry Reding wrote: > > > * Daniel Stone wrote: > > > > Heh, threads are always problematic. Are you calling XInitThreads() > > > > before your first call to XOpenDisplay()? > > > > > > Actually I was just using Gtk+, without any explicit calls to the X > > > libraries. But grep'ing through the Gtk+ sources yields no matches for > > > XInitThreads(). I'll try adding it manually. > > > > Calling XInitThreads() explicitly does indeed seem to solve the problem. > > I've > > been doing some more monkey-testing and wasn't able to reproduce this > > particular problem. > > Hurrah. :) > > > Still, in my opinion this should be something for Gtk+ to take care of. > > Would > > you agree that this should be filed as a bug report against Gtk+? > > I think gdk_threads_init() or similar takes care of this;
I cannot find any references to XInitThreads() in the GTK/GDK sources. gdk_threads_init() merely sets up gdk-specific locking. Are you saying the GDK threads support should be equivalent to the Xlib one? Or is this indeed missing in the GDK initialization? > GTK+ and threads are fraught anyway. Alas, this is not the first time I've run into this kind of trouble. In retrospect it might have been better to split off the different components instead of cramming it all into a single process. Then again, that would have been rather awkward. Thierry
pgp2tQ6zWrkxt.pgp
Description: PGP signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
