Problem 868 - particles inserted automatically during process definition cause segmentation violation
Summary: particles inserted automatically during process definition cause segmentation...
Status: RESOLVED INVALID
Alias: None
Product: Geant4
Classification: Unclassified
Component: particles (show other problems)
Version: 8.0
Hardware: PC Linux
: P5 minor
Assignee: kurasige
URL:
Depends on:
Blocks:
 
Reported: 2006-05-22 02:19 CEST by marc.vangoethem
Modified: 2006-06-06 22:13 CEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description marc.vangoethem 2006-05-22 02:19:35 CEST
I have been rewriting part of my physics list code and removed some (for me)
exotic particles which i thought i would not need (but they are appearently
needed in the final state of some processes). By adding processes some particles
got added (intentionally ?) to the  ParticleTable but they were not properly
defined. The ParticleTable::insert() function was never called for these
particles, therefor no process manager was made and the program exits with a
segmenation violation when calling the preparePhysicsTable() function using a
null pointer to the process manager to acces the processes list.

I am using GEANT4.8.0.p01 build on Linux-g++ (on Intel P4 and AMD64).
I've tried some of the examples from novice and advanced which compiled and
worked fine (no crashes).
Comment 1 kurasige 2006-05-25 23:44:59 CEST
In physics lists, you should define all particles and thier processes necessary
for your simulation. You SHOULD include all particles not only for initial
states but also final states.