Submitted by Anonymous (not verified) on Fri, 06/15/2012 - 12:07
I am developing a big application on RH7.3 Linux using g++ 2.93
compiler and also using open motif.
Sometimes, when I try to create a error dialog window, ui says
it core dumps at
(In the reverse order)
XmCreateErrorDialog
XtCreateWidget
....
....
....
XtFree
free
chunk_free
I have chekced all the parameters which are passed to XmCreateError Dialog, they are valid and correct, and no memory corruption is happening there.
But everytime, this happens, Please suggest how to detect, where
the problem is
Thanks in advance
B. Prabakaran
Hyderabad
‹ Tooltips and repaints and exposures... some explanations? How to create your own motif-resources (not the predefined.) ›
Mon, 11/03/2003 - 13:37#1
Segmentation Fault
You might want to make sure that the pointer to the prospective
dialog`s parent is allocated correctly (i.e. it`s not null and it has screen resources). The resources are obtained via any call to a "CreateWidget" method call.
steve orton
Mon, 11/03/2003 - 15:30#2
Segmentation Fault
There might also be a Motif/Glibc versioning problem here. The compiler you are using suggests that you are using an older Linux systems (perhap RH 6.1?). There was a glibc incompatibility introduced in the RH 7 series. Basically, mixing libraries compiled against different glibc would segfault. Try doing a Hello world button that just exits the application. If that works, you OK. If that also segfaults, you got a version problem.
If you want to stay on that release of Linux, you will need to yank the source code and do your own build. There are no recent builds of OM on Linux systems that old.
Mark
Mon, 11/03/2003 - 15:33#3
Segmentation Fault
Sorry, re-read, you`re on RH 7.3. But was that the right compiler version? RH 7.3 should be gcc 2.96 not 2.93.
Mark
Segmentation Fault
Hi Thanks for the quick reply
You are right it is 2.96 not 2.93 ( sorry ). I have written a
stand alone application, which creates 20 error dialogs simultaneously, and it did not result in segmentation violation.
But this is a big application, and I want to know due to what
reason it dumped.
I have checked the address of the widget passed to it, it is a
valid address.
Whether simultaneous updation of different popup widgets and the
main window will result in this kind of clash. Please help
Thanks in advance
B. Prabakaran