Submitted by kelvin on Fri, 11/02/2001 - 20:35. Developers
My application is crashed (Segmentation Core) and when I debug it, the line that gets a problem is XtAppNextEvent (In the mainLoop). Do anyone know about this problem? (My application have a lot of graphic, table). Thanks
Tue, 07/03/2012 - 13:22
#1
XtAppNextEvent problem!
It`s unlikely that the problem is really in that function. Rather, I suspect that you have bad memory accesses (writes) which are corrupting internal Xt data.
To debug this, you can certainly link with a version of Xt compiled with -d, so that you have complete debugging information. In addition, you can try the technique at http//www.motifzone.net/tnt/#object_destroy to see if it picks up any obvious problems. Thereafter, a tool such as Purify helps greatly.
Are you by any chance using XmTextField widgets to display dynamic data? We had a similar problem and traced it back our use of XmTextField in place of XmLabel, which we had done to eliminate update flicker when we changed the label string. Changing back to XmLabel solved the aborts, but now we have to live with the update flicker ( shrug ).