|Message: Re: G4FissionEvent Segmentation Error||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 have an update to my previous post concerning the segmentation fault on the method G4fissionEvent. I was still in doubt that the segmentation fault I was having was from G4fissionEvent. So i decided to use the gdb debugging too to determine which method was causing the G4fissionEvent to fail. Surprisingly, gdb point to G4fission::G4SmpIsoDir (i.e the method that samples the momentum direction for the neutron particle generated).
I honestly find it hard to believe that this is the source of the issue as I believe some other geant4 users have called this function in some fashion. As I mentioned earlier, the behavior I am noticing only occurs after a number of thousands of events have been ran.
Any response will be appreciated. Thanks.