|Message: Segmentation Error After A Number Of Events||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 am using geant4 to model spontaneous fission using the G4fissionEvent method. The way I have it setup is that in PrimaryGeneratorAction I have instantiated G4fissionEvent header and call the method in my GeneratePrimaries function (i.e a function which takes a pointer from G4Event as argument). This means that at the beginning of an event, G4fissionEvent is called and it produces a number of neutrons (i.e which is the particle of interest to my work). The issue I seem to be having is a Segmentation Fault after the application has completed a number of events successfully. I used the gdb debugger to try to narrow down which specific function associated with the G4fissionEvent might be causing the segfault and it reveals the method G4SmpIsoDir seems to be where the segfault is originating.|
As another way to confirm that my issue was really originating from G4SmpIsoDir I made a scale down copy (i.e removed all functions, methods or objects related to neutron generation) of the G4fissionEvent method and associated methods so that I can further troubleshoot the issue. I specifically commented out the function call to G4SmpIsoDir and ran my application. Although, apparently I did not get the result I was looking for, the application ran for 10 million events without a segmentation fault. I then un-commented the function call to G4SmpIsoDir and the went into the implementation file and commented out the de-referenced pointers where the value of the x-y-z component of the direction is stored. This also was segmentation fault free.
Based on what I have the only conclusion I am able to come to is that there is some issue with the G4SmpIsoDir.cc method but I can't say if it is related to how I use it or something else. Please can someone kindly share some ideas as to how to tackle this issue? Thank you.
|Inline Depth:||Outline Depth:||Add message:|