-
Notifications
You must be signed in to change notification settings - Fork 3.8k
[crashing] Remove Mono signal handlers when starting to handle a crash #17002
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
Conversation
|
@monojenkins build failed |
|
I wonder if |
| g_assert (sigaction (SIGCHLD, &sa, NULL) != -1); | ||
|
|
||
| /* Remove SIGQUIT, we are already dumping threads */ | ||
| g_assert (sigaction (SIGQUIT, &sa, NULL) != -1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
g_assert not supposed to have side effects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jaykrell This is some code that was moved and complemented, I did not want to make changes to the motif
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@monojenkins backport 2019-08 |
#17078) [2019-08] [crashing] Remove Mono signal handlers when starting to handle a crash Fixes #16803 Backport of #17002. /cc @marek-safar @alexischr
|
@monojenkins backport to 2019-06 |
|
@lambdageek backporting to 2019-06 failed, the patch results in conflicts: Please backport manually! |
Fixes #16803