|
|
 | | From: | christian mader | | Subject: | Unexpected async reply | | Date: | Thu, 20 Jan 2005 14:11:32 GMT |
|
|
 | How can I find out, which call causes the 'Xlib: unexpected async reply
(sequence 0x48b)!' message? I'm currently using the --sync option to start
my application, the message occurs when doing a wxTextCtrl in a wxFrame
that's created in the OnInit() function. It seems another GUI-Function is
called somewhere in my worker thread, but how could i find it? any
suggestions? gdb doesn't help very much :(
greetings
|
|
| | From: | Adam Hawes | | Subject: | Re: Unexpected async reply | | Date: | Fri, 21 Jan 2005 20:23:44 +1030 |
|
|
|
Hi there,
>How can I find out, which call causes the 'Xlib: unexpected async reply
>(sequence 0x48b)!' message? I'm currently using the --sync option to start
>my application, the message occurs when doing a wxTextCtrl in a wxFrame
>that's created in the OnInit() function. It seems another GUI-Function is
>called somewhere in my worker thread, but how could i find it? any
>suggestions? gdb doesn't help very much :(
This comes up again and again... you are obviously using wxGTK and
trying to do GUI things in a non-GUI thread. You have to remember
that wxBitmap is a GUI task. Updating controls is a GUI task.
Reading the value of controls is a GUI task.
Just search put a small fortune of printf()'s in your code and find
the line where it craps out. You'll probably want to make them very
specific printf's so it's easy to find which ones get executed and
which don't.
A
|
|
|
