Bug #688
import ErrorHandler => segmentation fault
Start date:
26 August 2011
Due date:
% Done:
0%
Estimated time:
Workflow:
Description
If I import ErrorHandler in simulate_mice.py before I import MAUS I get a segmentation fault. Sample code
import io import json import MAUS ### <<< ordering here causes Segmentation fault import ErrorHandler ### <<< ordering here causes Segmentation fault SIM_ARGS = None def run(): global SIM_ARGS input_file = io.StringIO(unicode(json.dumps({"mc": []}))) my_input = MAUS.InputPyJSON(input_file) my_map = MAUS.MapPyGroup() my_map.append(MAUS.MapPyBeamMaker()) # input beam my_map.append(MAUS.MapCppSimulation()) # geant4 simulation my_output = MAUS.OutputPyJSON(open("simulation.out", 'w')) datacards = open('input.py') SIM_ARGS = (my_input, my_map, MAUS.ReducePyDoNothing(), my_output, datacards) if __name__ == '__main__': run() MAUS.Go(*SIM_ARGS)
Updated by Tunnell, Christopher over 12 years ago
shouldn't we be doing that import within the MAUS import? SConstruct generates that file
Updated by Rogers, Chris over 12 years ago
This is the simulate_mice.py in MAUS_ROOT_DIR/bin. Maybe we should do
import MAUS from MAUS import ErrorHandler
or whatever, but doesnt matter it shouldn't make a segmentation fault. Also, this is something to do with the way I do communication between cpp and python stuff, so would like to iron that out in case (when) I want to make more stuff that talks between the two.
Updated by Rogers, Chris over 12 years ago
- Target version changed from Future MAUS release to MAUS-v0.1.0
Updated by Rogers, Chris about 12 years ago
I did the python interface for evaluator in different, better way... probably would fix this issue.
Updated by Rogers, Chris about 12 years ago
- Status changed from Open to Rejected
Just trying to repeat this error and failing, so reject.
Updated by Rogers, Chris about 12 years ago
- Target version changed from MAUS-v0.1.0 to MAUS-v0.0.9