ConsoleAgent: Log unexpected signals to stderr #86
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
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.
Hi,
Currently, eshost (and eshost-cli) doesn't log unexpected signals (e.g., SIGSEGV) from the child process. As some of the supported JS engines are still in development, this can suppress errors when the engine seg-faults. At this time, seg-faulting test-cases have no output on affected engines and appear to exit successfully.
I noticed SIGKILL was used internally for process control, so my patch captures all signals other than SIGKILL.
This PR should also provide better support for eshost-cli e.g., bterlson/eshost-cli#55
Thank you!