Signal handling #10
Merged
Signal handling #10
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
- Use signal_deliver instead of signal_generate tracepoint to avoid locking the mutex while the signal spinlock is held - Properly suspend on and cancel (non-fatal) signals - Add __get_debugger and __get_victim to allow accessing debugger and victim entries without automatically generating them (they return NULL if the entry does not exist)
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.
A new event type
EVENT_SIGNALis sent whenever a debugged process receives a signal (when enabled in the event mask). If a process is suspended on a signal (SUSPEND_ON_SIGNAL), issuing thecancel_signalcommand will stop the signal from being delivered to the process. Note that this is a destructive (but idempotent) operation; issuing the command from multiple debuggers should not result in errors.