Re: Xlib: unexpected async reply (sequence 0x47)!

[Jean-Marc Valin <jean-marc valin hermes usherb ca>]

I get this message every once and then... I means that you are making two X
calls (or gtk calls) at the same time, without protecting your stuff... Your
program should start by calling:
g_thread_init(NULL);

Your gtk_main() should be:
gdk_thread_enver();
gtk_main();
gdk_thread_leave();

and you should also protect all gtk calls that aren't in the main thread with
the gdk_thread_enter/gdk_thread_leave calls.

For more info, there's a "threaded Hello World" somewhere. Also beware that glib
2.1.6 has a bug that makes some threaded programs deadlock.

	Jean-Marc

Hassan Aurag a écrit :
> 
>  Hi,
> 
> The subject with the exclamation and all is the message I get
> sometimes when using the software I code. I suspect it has to do with
> threads that I use for very stupid things like making fifos so that
> processes can communicate but in truth I have no idea what this beast
> is.
> 
>  So what the heck does it mean to have:
> Xlib: unexpected async reply (sequence 0x47)!
> 
> Thanks in advance,
> 
> --
> To unsubscribe: mail gnome-devel-list-request@gnome.org with "unsubscribe"
> as the Subject.

-- 
Jean-Marc Valin
Universite de Sherbrooke - Genie Electrique
valj01@gel.usherb.ca