Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@monojenkins
Copy link
Contributor

install_state_summarizer installs a SIGTERM handler. Unfortunately sigterm_signal_handler assumes that it will only be called when a crash is already in progress (it assumes it won't be the supervisor, and so it doesn't setup the memory for capturing a crash report among other things).

Addresses #17271

Backport of #17296.

/cc @lambdageek

install_state_summarizer installs a SIGTERM handler. Unfortunately
sigterm_signal_handler assumes that it will only be called when a crash is
already in progress (it assumes it won't be the supervisor, and so it doesn't
setup the memory for capturing a crash report among other things).
Previously it was installed by EnableMicrosoftTelemetry, which is too early.
Now we get here without a handler installed even when mono_merp_enabled returns true.
@lambdageek lambdageek changed the title [master] [2019-06][merp] Don't install SIGTERM handler in EnableMicrosoftTelemetry [master][merp] Don't install SIGTERM handler in EnableMicrosoftTelemetry Oct 14, 2019
@lambdageek
Copy link
Member

On master we may want to investigate the options that Jay suggested:

install the handler at the same time, but use a boolean to enable/disable it

@lambdageek lambdageek self-assigned this Oct 15, 2019
lambdageek added a commit to lambdageek/mono that referenced this pull request Oct 23, 2019
lambdageek pushed a commit that referenced this pull request Oct 26, 2019
…ior when dumping (#17537)

* dump_native_stacktrace should always register the sigterm handler.

Cherry picked from the #17310

* [merp] Introduce a new 'dump mode' that allows different signal behavior when dumping

The primary reason for this is gaining the ability to interpret SIGTERM properly as a crashing signal when outside of 'dump mode', and as a utility signal during the 'thread summarizer' dumping process.
@lambdageek
Copy link
Member

Don't need this anymore. Obsoleted by #17537

@lambdageek lambdageek closed this Oct 29, 2019
ManickaP pushed a commit to ManickaP/runtime that referenced this pull request Jan 20, 2020
…ior when dumping (mono/mono#17537)

* dump_native_stacktrace should always register the sigterm handler.

Cherry picked from the mono/mono#17310

* [merp] Introduce a new 'dump mode' that allows different signal behavior when dumping

The primary reason for this is gaining the ability to interpret SIGTERM properly as a crashing signal when outside of 'dump mode', and as a utility signal during the 'thread summarizer' dumping process.



Commit migrated from mono/mono@db568c6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants