Fix issues with .NET using signals as runtime instruments - #301
Merged
Conversation
E.g. SIGXCPU is used to trigger garbage collection, and would spam stderr if left in place (not to mention terminate when it shouldn't). SIGSEGV is used for checking null pointer exceptions, etc.
They both support finding the file, and for our image it will be present
pasin
approved these changes
Jun 2, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
E.g. SIGXCPU is used to trigger garbage collection, and would spam stderr if left in place (not to mention terminate when it shouldn't). SIGSEGV is used for checking null pointer exceptions, etc.
The solution is to NOT call exit and instead be a good citizen in the bizarro world that is unix signal handling and just call the previous handler and defer to their authority.