-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
lib: crash handlers must be allowed on threads #18060
Merged
donaldsharp
merged 1 commit into
FRRouting:master
from
opensourcerouting:lib-crashlog-signals
Feb 11, 2025
Merged
lib: crash handlers must be allowed on threads #18060
donaldsharp
merged 1 commit into
FRRouting:master
from
opensourcerouting:lib-crashlog-signals
Feb 11, 2025
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
Blocking all signals on non-main threads is not the way to go, at least the handlers for SIGSEGV, SIGBUS, SIGILL, SIGABRT and SIGFPE need to run so we get backtraces. Otherwise the process just exits. Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
4d11601
to
13a6ac5
Compare
@Mergifyio backport dev/10.3 stable/10.2 stable/10.1 stable/10.0 stable/9.1 stable/8.4 |
✅ Backports have been created
|
This was referenced Feb 11, 2025
Jafaral
added a commit
that referenced
this pull request
Feb 12, 2025
lib: crash handlers must be allowed on threads (backport #18060)
Jafaral
added a commit
that referenced
this pull request
Feb 12, 2025
lib: crash handlers must be allowed on threads (backport #18060)
Jafaral
added a commit
that referenced
this pull request
Feb 12, 2025
lib: crash handlers must be allowed on threads (backport #18060)
Jafaral
added a commit
that referenced
this pull request
Feb 12, 2025
lib: crash handlers must be allowed on threads (backport #18060)
donaldsharp
added a commit
that referenced
this pull request
Feb 12, 2025
lib: crash handlers must be allowed on threads (backport #18060)
donaldsharp
added a commit
that referenced
this pull request
Feb 12, 2025
lib: crash handlers must be allowed on threads (backport #18060)
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.
You can have the prettiest crash handler on the planet, if you go and mask SIGSEGV on a thread before it segfaults… YOU GET NOTHING, YOU LOSE, GOOD DAY SIR.
(The process just up and hard exits.)
…let's see which of our CI systems don't recognize which of the signals I listed in here…