cheribsdtest: Improve reason if child unexpectedly dies with a signal #1737
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
Currently we just use "Child exited abnormally" for when the child process doesn't exit cleanly, which is unhelpful when debugging, so print the signal number instead if it was due to a signal. Note that tests which deliberately provoke signals still exit cleanly, since the child's test harness will catch the signal, save various parts of the given siginfo_t and exit. This code is only for more catastrophic situations (e.g. signal delivery itself is broken or the child received a fatal signal before even setting up the handler).
bsdjhb
approved these changes
Jul 6, 2023
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.
Currently we just use "Child exited abnormally" for when the child process doesn't exit cleanly, which is unhelpful when debugging, so print the signal number instead if it was due to a signal.
Note that tests which deliberately provoke signals still exit cleanly, since the child's test harness will catch the signal, save various parts of the given siginfo_t and exit. This code is only for more catastrophic situations (e.g. signal delivery itself is broken or the child received a fatal signal before even setting up the handler).