Submitted by Anonymous on Mon, 08/04/2003 - 19:53.
hi. my application is hanging. when i kill it, the stack trace is
#0 0x90025788 in select ()
#1 0x964760a4 in _XtWaitForSomething ()
#2 0x96477150 in XtAppNextEvent ()
#3 0x9646dc3c in XtAppMainLoop ()
how can i debug this? i think it _may_ have something to do with glx, but i have not way of knowing for sue. i am very curious as to what resouce the select() statement is waiting for but never getting.
m.
Mon, 08/04/2003 - 22:56#1
Anonymous
Hanging on XtAppMainLoop() how to debug?
First of all, how do you know that you application is hanging? It may just be waiting for user input.... Some things that come to mind are have any widgets grabbed the keyboard and/or mouse focus, and what do the widgets do? If there is a bug in the code for how you wrote those widgets, there may be no way to enter in any input (and, thus, the program will appear to hang).
Also, do you have callbacks for your widgets, (I would double check the call backs, and maybe print out some info in your code to try and figure out what it did last). You may also want to write your own main loop with some print statements to figure out what is going on...
Good luck,
alm
Wed, 08/06/2003 - 02:26#2
ICS_support
Hanging on XtAppMainLoop() how to debug?
The stack trace is probably not correct. Such a trace usually indicates a memory-write error.
The way to debug this is to use a -d version of libXt; you`ll get a better stack trace. You can also set breakpoints at appropriate spots.