Project

General

Profile

Bug #593

Simulation fails with multiple primaries in the same spill

Added by Rogers, Chris about 12 years ago. Updated about 12 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Rogers, Chris
Category:
Simulation
Target version:
Future MAUS release
Start date:
21 July 2011
Due date:
% Done:

0%

Estimated time:
Workflow:

Description

Some weird g4 behaviour when I put multiple primaries in the same spill - primaries after the first are not tracked. See attached run script, log, output.

Files

simulate_mice_test.py (2.82 KB) simulate_mice_test.py Run script Rogers, Chris, 21 July 2011 08:21
simulate_mice_test.log (1.64 KB) simulate_mice_test.log log file (stdout, stderr) Rogers, Chris, 21 July 2011 08:21
simulation.out (2.42 MB) simulation.out json output Rogers, Chris, 21 July 2011 08:21
valgrind.log (352 KB) valgrind.log Rogers, Chris, 27 July 2011 14:29
#1

Updated by Rogers, Chris about 12 years ago

Works okay on 32 bit but not on 64 bit - indeed, it now crashes with segmentation fault in 64 bit. Valgrind log attached. Looks like json or potentially geant4. I'll try to get Valgrind working on my 64 bit machine so I can see what's going on there. (Nb: python is not compatible with valgrind - has it's own malloc system. Assume the native C++ stuff is not affected by this, but the python stuff is).

#2

Updated by Rogers, Chris about 12 years ago

  • Status changed from Open to Rejected
  • % Done changed from 0 to 100

Humm, think it must have been some problem with my dev environment. Works fine in my trunk copy and no memory problems registered...

Also available in: Atom PDF