Bug #593
Simulation fails with multiple primaries in the same spill
Status:
Rejected
Priority:
Normal
Assignee:
Category:
Simulation
Target version:
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
Updated by Rogers, Chris about 12 years ago
- File valgrind.log valgrind.log added
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).
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...