|Message: Segmentation fault during decay chain simulation||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
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*) ()