Problem 1370 - FanoCavity2 with QT ON, OpenInventor OFF on FC14, geant4-09-05-ref-10
Summary: FanoCavity2 with QT ON, OpenInventor OFF on FC14, geant4-09-05-ref-10
Status: CLOSED FIXED
Alias: None
Product: Examples/Extended
Classification: Unclassified
Component: medical/fanoCavity,2 (show other problems)
Version: 9.5
Hardware: All Linux
: P5 normal
Assignee: garnier
URL:
: 1371 (view as problem list)
Depends on:
Blocks:
 
Reported: 2012-11-08 15:27 CET by garnier
Modified: 2013-02-26 23:37 CET (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description garnier 2012-11-08 15:27:32 CET
From Ivana : 

/vis/viewer/create ! ! 600x600-0+0
[New Thread 0x7fffeb33f700 (LWP 21899)]
[New Thread 0x7fffe9306700 (LWP 21900)]
Detaching after fork from child process 21901.

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
...
#0  0x0000000000000000 in ?? ()
#1  0x00007ffff70b83b9 in G4OpenGLStoredQtViewer::Initialise() ()
  from /work/packages/geant4/geant4_ref_install/lib64/libG4OpenGL.so
#2  0x00007ffff6c0a07d in G4VisManager::CreateViewer(G4String, G4String) ()
  from /work/packages/geant4/geant4_ref_install/lib64/libG4vis_management.so
#3  0x00007ffff6bf23d5 in G4VisCommandViewerCreate::SetNewValue(G4UIcommand*, G4String) ()
  from /work/packages/geant4/geant4_ref_install/lib64/libG4vis_management.so
#4  0x00007ffff23255c0 in G4UIcommand::DoIt(G4String) ()
  from /work/packages/geant4/geant4_ref_install/lib64/libG4intercoms.so
Comment 1 garnier 2012-11-08 15:32:01 CET
On Mac OS 10.8 the problem is not the same :


# Re-establish auto refreshing and verbosity:
/vis/viewer/set/autoRefresh true
/vis/viewer/refresh
/vis/verbose warnings
Visualization verbosity changed to warnings (3)
#
# For file-based drivers, use this to create an empty detector view:
#/vis/viewer/flush
Available UI session types: [ Qt, Xm, GAG, tcsh, csh ]
G4UIQt : Unable to init Qt. Aborted

Graphics systems deleted.
Comment 2 Ivana Hrivnacova 2012-11-14 16:15:05 CET
A work-around for this problem was to re-order instantiating G4VisExecutive and G4UIExecutive in main so that G4UIExecutive is created before calling vis.mac macro.

The main was changed in this way in the following extended examples:
analysis/AnaEx03
eventgenerator/particleGun
medical/fanoCavity2,GammaTherapy
radioactivedecay/rdecay01

It would be good to add a check in VIS/UI drivers so that in case of a wrong order of creating UI/Vis executive objects, user gets an exception with a meaningful message, before the program stop.
Comment 3 garnier 2012-11-14 18:07:08 CET
*** Problem 1371 has been marked as a duplicate of this problem. ***
Comment 4 garnier 2012-11-21 17:58:46 CET
Ok, FIXED by Ivana,
Comment 5 Koichi Murakami 2013-02-26 23:37:42 CET
The issue was moved to JIRA.
http://jira-geant4.kek.jp/browse/DEV-11