-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add unconditional warning before handling StackOverflow #54622
Conversation
Same with InterruptException then? Regarding the message I don't know if anyone will really understand the meaning of "which may result in problems for the program.". |
Yeah, I wanted people to have realistic expectations that this is not within the guarantees to program behavior. The ^C has some similar issues, but I don't want to print as much text (just the ^C) for that case. Happy to take other wording suggestions, as I didn't like this much, but couldn't think of anything more clear. |
Avoids a race condition where a signal (e.g. StackOverflowError) happens while trying to initialize the rest of the frame, resulting in trying to longjmp to garbage.
Since this is not modeled by the exception logic, and it can interrupt arbitrary program state or corrupt locks (leading to hangs and other issues), as well as just frequently segfaulting afterwards, give a printed message as soon as we notice things are going badly before attempting to recover.
491f900
to
21b1e15
Compare
Well that is curious, I didn't expect this PR to already help clarify a possible cause of a crash in CI (rr trace included for reproducer);
|
Since this is not modeled by the exception logic, and it can interrupt arbitrary program state or corrupt locks (leading to hangs and other issues), as well as just frequently segfaulting again afterwards, give a printed message as soon as we notice things are going badly before attempting to recover. For example:
Refs #52291