Fix G4VExceptionHandler lifetime and improve exception wrapping #773
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sethrj
added
bug
pcanal
requested changes
May 30, 2023
pcanal
approved these changes
May 30, 2023
|
Thanks @pcanal ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because
G4VExceptionHandlerpermanently saves a pointer to itself, callingG4ExceptionafterGeantExceptionHandlerexited scope would cause the code to segfault. A new public wrapper classScopedGeantExceptionHandler, which is safe to use even if Geant4 is disabled, should correctly save and restore the original exception handler to prevent this from occurring.While testing #759 I also hit some exceptions inside the transport loop in the step collector tests, so I unified the stepper loops in those and wrapped with
LogKernelException.