Message: Segmentation fault during decay chain simulation Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Segmentation fault during decay chain simulation 

Forum: User Requirements
Date: 07 Sep, 2018
From: <kwarnello>

I use Geant4 in MT for simulation of a background from various elements of a detector and shielding. I regularly have a "Segmentation fault (core dumped)" crash, once every 1e+8 or so of events. Error occurs at beginning of my simulation or sometimes a few runs end without crash.

I mainly simulate decay chain of U-238, Th-228, K-40 and so on. My physics list is based on /extended/radioactivedecay/rdecay02 but I have adjusted a few things, that I listed below: - G4EmStandardPhysics() for G4EmStandardPhysics_option3() (but crash also occurs with Livermore and option4 EM physics), - Electron and Muon Nuclear changed at true at G4EmExtraPhysics, - registered G4ThermalNeutrons() physics, - changed CutValue from 10*km -> 3*mm for default (also other cuts for different regions of geometry).

I checked applied geometry with /geometry/test/run, no overlaps were detected. I have tried Geant4 10.4_Patch-02 and 10.5-beta and the problem however exists. I tried to generate isotopes inside complex volumes using G4Navigator (something like in the underground_physics example) and gps with /gps/pos/confine command. Nothing changed.

I collected information about segmentation fault with GDB which I included at the end.

Do you have any ideas what can cause this problem?

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./rdecay02 gamma.mac'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f2efbaf2090 in G4VelocityTable::Value(double) ()
   from /home/k/sources/geant4.10.05/geant4.10.05.b01-install/lib/libG4track.so
[Current thread is 1 (Thread 0x7f2ec7b12700 (LWP 17673))]
(gdb) backtrace
#0  0x00007f2efbaf2090 in G4VelocityTable::Value(double) ()
   from /home/k/sources/geant4.10.05/geant4.10.05.b01-install/lib/libG4track.so
#1  0x00007f2efbae95ac in G4ParticleChangeForLoss::UpdateStepForAlongStep(G4Step*) ()
   from /home/k/sources/geant4.10.05/geant4.10.05.b01-install/lib/libG4track.so
#2  0x00007f2efe03958e in G4SteppingManager::InvokeAlongStepDoItProcs() ()
   from /home/k/sources/geant4.10.05/geant4.10.05.b01-install/lib/libG4tracking.so
#3  0x00007f2efe034ee3 in G4SteppingManager::Stepping() ()
   from /home/k/sources/geant4.10.05/geant4.10.05.b01-install/lib/libG4tracking.so
#4  0x00007f2efe045c83 in G4TrackingManager::ProcessOneTrack(G4Track*) ()
   from /home/k/sources/geant4.10.05/geant4.10.05.b01-install/lib/libG4tracking.so
#5  0x00007f2efe27f917 in G4EventManager::DoProcessing(G4Event*) ()
   from /home/k/sources/geant4.10.05/geant4.10.05.b01-install/lib/libG4event.so
#6  0x00007f2efe5440ac in G4WorkerRunManager::DoEventLoop(int, char const*, int) () from /home/k/sources/geant4.10.05/geant4.10.05.b01-install/lib/libG4run.so
#7  0x00007f2efe53114b in G4RunManager::BeamOn(int, char const*, int) ()
   from /home/k/sources/geant4.10.05/geant4.10.05.b01-install/lib/libG4run.so
#8  0x00007f2efe548c89 in G4WorkerRunManager::DoWork() ()
   from /home/k/sources/geant4.10.05/geant4.10.05.b01-install/lib/libG4run.so
#9  0x00007f2efe558a13 in G4MTRunManagerKernel::StartThread(G4WorkerThread*) ()

 Add Message Add Message
to: "Segmentation fault during decay chain simulation"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews


[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]