|Message: Strange Segmentation fault||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 have discovered the very strange behaviour of my program when I tried to run a few particles just for a check with visualisation.
With G4MULTITHREADED if the number of events is very small, Geant4 splits work in the following way for 4 threads:
G4WT3 > ### Run 0 starts on worker thread 3. .... G4WT0 > ### Run 0 starts on worker thread 0. G4WT3 > Going to create slave ntuples from main .... G4WT0 > Going to create slave ntuples from main G4WT3 > Thread-local run terminated. .... G4WT0 > Thread-local run terminated. G4WT3 > Run Summary G4WT1 > Run Summary G4WT2 > Run Summary G4WT2 > Number of events processed : 0 G4WT2 > User=0s Real=0s Sys=0s G4WT1 > Number of events processed : 4 G4WT0 > Run Summary G4WT3 > Number of events processed : 1 G4WT3 > User=0s Real=0s Sys=0s G4WT1 > User=0s Real=0s Sys=0s G4WT0 > Number of events processed : 0 G4WT0 > User=0s Real=0s Sys=0s G4VIS > G4VisManager: Using G4TrajectoryDrawByCharge as fallback trajectory model. G4VIS > See commands in /vis/modeling/trajectories/ for other options.
As a result:
Segmentation fault (core dumped)
Without output like this:
Run terminated. Run Summary Number of events processed : 600 User=0.09s Real=0.6s Sys=0.08s
Usually, it happens for Nevents<500 during the first run. Further, it works correctly: #1 Run - 1000 #2 Run - 50(No segmentation fault)
With G4RunManager instead of G4MTRunManager, it doesn't happen. Quite interesting to know the reason. Maybe something with short processing times?
G4WT1 > User=0s Real=0s Sys=0s
|Inline Depth:||Outline Depth:||Add message:|