From: Jacek M. Holeczek (holeczek@us.edu.pl)
Date: Fri Nov 05 2004 - 14:15:41 MET

Maybe someone has met the following problem (root v4.00.08 / slc3,

When using the G4UI Xaw based session :
### Run 0 start.
Start Run processing.

---> Begin of event: 0

--------- Ranecu engine status ---------
 Initial seed (index) = 0
 Current couple of seeds = 9876, 54321
---> End of event: 0
Run terminated.
Run Summary
  Number of events processed : 1
  User=20s Real=25s Sys=3.2s

 *** Break *** segmentation violation
 Generating stack trace...
 0x01264961 in <unknown> from /usr/X11R6/lib/libX11.so.6
 0x01225893 in XFindContext + 0xc3 from /usr/X11R6/lib/libX11.so.6
 0x06258dea in <unknown> from /usr/X11R6/lib/libXaw.so.7
 0x0625b5b3 in <unknown> from /usr/X11R6/lib/libXaw.so.7
 0x0624ebaf in <unknown> from /usr/X11R6/lib/libXaw.so.7
 0x0423ba3a in <unknown> from /usr/X11R6/lib/libXt.so.6
 0x0423bf78 in <unknown> from /usr/X11R6/lib/libXt.so.6
 0x0423c573 in _XtTranslateEvent + 0x83 from /usr/X11R6/lib/libXt.so.6
 0x04214834 in XtDispatchEventToWidget + 0x184 from /usr/X11R6/lib/libXt.so.6

When using the G4UI Xm based session :

 *** Break *** segmentation violation
 Generating stack trace...
 0x011a4961 in <unknown> from /usr/X11R6/lib/libX11.so.6
 0x01165893 in XFindContext + 0xc3 from /usr/X11R6/lib/libX11.so.6
 0x085711de in _XmGetWidgetExtData + 0x4e from /usr/X11R6/lib/libXm.so.3
 0x0856c02f in _XmGetFocusData + 0x7f from /usr/X11R6/lib/libXm.so.3
 0x0856af95 in _XmNavigSetValues + 0x25 from /usr/X11R6/lib/libXm.so.3
 0x085686d8 in <unknown> from /usr/X11R6/lib/libXm.so.3
 0x031d56f3 in <unknown> from /usr/X11R6/lib/libXt.so.6
 0x031d56ac in <unknown> from /usr/X11R6/lib/libXt.so.6
 0x031d5c33 in XtSetValues + 0x323 from /usr/X11R6/lib/libXt.so.6
 0x08503a36 in <unknown> from /usr/X11R6/lib/libXm.so.3
 0x085965e4 in _XmSFUpdateNavigatorsValue + 0xa4 from /usr/X11R6/lib/libXm.so.3
 0x08522269 in _XmChangeVSB + 0x109 from /usr/X11R6/lib/libXm.so.3
 0x08522f69 in <unknown> from /usr/X11R6/lib/libXm.so.3

It seems that it happens only when from inside of the Geant4 application I
make "new TApplication("Application", ((int *)0), ((char **)0));" and then
I create and draw a TCanvas.
Is it possible that the X11 handling by both the ROOT and G4UI is a
problem nowadays?

It is possibly worth of noting that ... in case of Xaw based G4UI it dies
AFTER the event is fully processed (the canvas has been created and
refreshed all the time as expected), while in case of Xm based G4UI it
dies shortly after the canvas is created and drawn (in the beginning of
the event processing).

Any ideas?
Thanks in advance,
Best regards,

This archive was generated by hypermail 2b29 : Sun Jan 02 2005 - 05:50:10 MET