Skip to content

[runtime] Report crash when receiving crashing signals #2052

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

Merged
merged 1 commit into from
Feb 6, 2020

Conversation

monojenkins
Copy link
Contributor

This PR is synchronized with mono/mono#18243.
Do not edit this PR, changes here are overwritten when pushing to the other PR.
Please merge both PRs at the same time.



The default handlers for SIGTRAP, SIGSYS on macOS and Linux crash the process, so we now have Mono report this.

This change also changes the presentation of the signal name on the stacktrace report dumped on error (from e.g. "SIGSEGV" to "segv").

@monojenkins monojenkins force-pushed the sync-pr-18243-from-mono branch 12 times, most recently from a9ebdad to e948bad Compare January 29, 2020 02:08
The default handlers for SIGTRAP, SIGSYS on macOS and Linux crash the process, so we now have Mono report this.

This change also changes the presentation of the signal name on the stacktrace report dumped on error (from e.g. "SIGSEGV" to "segv").
@monojenkins monojenkins force-pushed the sync-pr-18243-from-mono branch from e948bad to 635a990 Compare February 3, 2020 14:19
@lambdageek lambdageek marked this pull request as ready for review February 3, 2020 21:32
@lambdageek lambdageek merged commit 8c941a5 into dotnet:master Feb 6, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants