| commit | 58d5e154b7eb18e4c9b67236a555a2ec20bbe0d0 | |
| author | Alexander Kyte <alexmkyte@gmail.com> | |
| Tue, 30 Oct 2018 18:24:38 +0000 (30 14:24 -0400) | ||
| committer | Alexander Köplinger <alex.koeplinger@outlook.com> | |
| Tue, 30 Oct 2018 18:24:38 +0000 (30 19:24 +0100) | ||
| tree | 733d3953cbc4674cede5ed28bd446e043348afd3 | treesnapshot (tar.gz zip) |
| parent | 263e59de6500b4a6417554e1c7a7f23cf44ddba8 | commitdiff |
[crash] Fix merp invocation (#11435)
The change which made the handler return (rather than crashing the
runtime) did not consider this control flow path that causes the sigterm
signal handler to trigger the merp dumper if we return.
We now always return.
This was previously so that a random sigterm could be used to trigger a
dump. This isn't really used, and won't work right now anyways
(we don't register it until right before we dump). My fix is to remove
it, and to make the signal handler only work as part of the dumper
machinery.
The change which made the handler return (rather than crashing the
runtime) did not consider this control flow path that causes the sigterm
signal handler to trigger the merp dumper if we return.
We now always return.
This was previously so that a random sigterm could be used to trigger a
dump. This isn't really used, and won't work right now anyways
(we don't register it until right before we dump). My fix is to remove
it, and to make the signal handler only work as part of the dumper
machinery.
| mono/mini/mini-posix.c | diffblobblamehistory |