|Message: Do G4Exception severities trigger the actions they describe?||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 writing some new physics process code. In some corner situations, I end up with a badly configured track (specifically, a null pointer to a lookup table) and the track or event should be aborted as a result.
I've written a proper G4Exception to that effect, using "EventMustBeAborted" as the severity code ("Error happens during tracking a particle. The event currently being processed should be aborted, run will not be aborted."), but nothing happens except that the exception message is printed out. The code proceeds through and I get the same segfault I was getting before adding the G4Exception.
The header file G4ExceptionSeverity.hh describes the five severity levels -- FatalException, FatalErrorInArgument, RunMustBeAborted, EventMustBeAborted, JustWarning -- and what should happen in the job as a result of each of them. However, it seems like only the two "Fatal" levels actually trigger a failure. The other three, instead of affecting the event loop, just print a message and proceed.
Is this the expected behaviour? I'm building against 10.2 patch-01.
-- Mike Kelsey