[Gate-users] Segmentation violation with QGSP_INCLXX

Albert Hirtl albert.hirtl at tuwien.ac.at
Mon Sep 14 10:06:33 CEST 2015


Dear Friends,

I am having some issue with the physics list QGSP_INCLXX. If I use that 
one I always get a segmentation violation. If I use, e.g., QGSP_BIC or 
QGSP_BERT everything is fine. The output I get is the following:

..........

### === G4UAtomicDeexcitation::InitialiseForNewRun()
### ===  PIXE model for hadrons: Empirical  1
### ===  PIXE model for e+-:     Livermore  1
[Core-0] End of macro mac/main.mac
Graphics systems deleted.
Visualization Manager deleting...

  *** Break *** segmentation violation



===========================================================
There was a crash.
This is the entire stack trace of all threads:
===========================================================
#0  0x00007f3dac0af66a in waitpid () at /lib64/libc.so.6
#1  0x00007f3dac02aa3b in do_system () at /lib64/libc.so.6
#2  0x00007f3db81d4334 in TUnixSystem::StackTrace() () at 
/opt/simulation/root_5_34_30/lib/libCore.so
#3  0x00007f3db81d645c in TUnixSystem::DispatchSignals(ESignals) () at 
/opt/simulation/root_5_34_30/lib/libCore.so
#4  0x00007f3dac01ba50 in <signal handler called> () at /lib64/libc.so.6
#5  0x00007f3dac06bf0b in malloc_usable_size () at /lib64/libc.so.6
#6  0x00007f3db27f6f39 in  () at /usr/lib64/nvidia/libGL.so.1
#7  0x00007f3dab06a0d9 in  () at 
/usr/lib64/nvidia/tls/libnvidia-tls.so.352.41
#8  0x00007f3daf382c49 in G4CrossSectionDataSetRegistry::Clean() () at 
/opt/simulation/geant4_10_01_p02/lib64/libG4processes.so
#9  0x00007f3daf3bd08e in 
G4HadronicProcessStore::~G4HadronicProcessStore() () at 
/opt/simulation/geant4_10_01_p02/lib64/libG4processes.so
#10 0x00007f3daf3be6cd in 
G4ThreadLocalSingleton<G4HadronicProcessStore>::~G4ThreadLocalSingleton() () 
at /opt/simulation/geant4_10_01_p02/lib64/libG4processes.so
#11 0x00007f3dac020648 in __run_exit_handlers () at /lib64/libc.so.6
#12 0x00007f3dac020695 in  () at /lib64/libc.so.6
#13 0x00007f3dac007707 in __libc_start_main () at /lib64/libc.so.6
#14 0x0000000000528019 in _start ()
===========================================================


The lines below might hint at the cause of the crash.
If they do not help you then please submit a bug report at
http://root.cern.ch/bugs. Please post the ENTIRE stack trace
from above as an attachment in addition to anything else
that might help us fixing this issue.
===========================================================
#5  0x00007f3dac06bf0b in malloc_usable_size () at /lib64/libc.so.6
#6  0x00007f3db27f6f39 in  () at /usr/lib64/nvidia/libGL.so.1
#7  0x00007f3dab06a0d9 in  () at 
/usr/lib64/nvidia/tls/libnvidia-tls.so.352.41
#8  0x00007f3daf382c49 in G4CrossSectionDataSetRegistry::Clean() () at 
/opt/simulation/geant4_10_01_p02/lib64/libG4processes.so
#9  0x00007f3daf3bd08e in 
G4HadronicProcessStore::~G4HadronicProcessStore() () at 
/opt/simulation/geant4_10_01_p02/lib64/libG4processes.so
#10 0x00007f3daf3be6cd in 
G4ThreadLocalSingleton<G4HadronicProcessStore>::~G4ThreadLocalSingleton() () 
at /opt/simulation/geant4_10_01_p02/lib64/libG4processes.so
#11 0x00007f3dac020648 in __run_exit_handlers () at /lib64/libc.so.6
#12 0x00007f3dac020695 in  () at /lib64/libc.so.6
#13 0x00007f3dac007707 in __libc_start_main () at /lib64/libc.so.6
#14 0x0000000000528019 in _start ()
===========================================================


Does anyone have any idea what is wrong here? I compiled gate7.1 against 
geant4-10-01-patch-02 (also tried with geant4_10_01) and root_5_34_30. 
In principle the simulation seems to be ok - if I run it with 
/control/execute it finishes without complaint. Only once I exit Gate I 
get the seg. fault, which I of course always get when running it from 
command line with "Gate main.mac". It leaves a bit a bad feeling, however.

Help is much appreciated.

Best regards,
Albert

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengatecollaboration.org/mailman/private/gate-users/attachments/20150914/59655f7d/attachment.html>


More information about the Gate-users mailing list