| commit | 502567f2f5ee10f98a62d1f399628468c5d4388b | |
| author | primiano <primiano@chromium.org> | |
| Mon, 1 Dec 2014 12:52:42 +0000 (1 04:52 -0800) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Mon, 1 Dec 2014 12:52:55 +0000 (1 12:52 +0000) | ||
| tree | e8270079bed296e94288597af75be40a2affb1e2 | treesnapshot (tar.gz zip) |
| parent | bbb9c85bbcff205711e96ee6273f7c6fcd4db449 | commitdiff |
[android] Fix SIGABRT handling in the WebView crash handler.
The WebView fingerprint crash handler introduced in crrev.com/678763005
was failing to cover the case of signals delivered through kill/raise.
Conversely to what happens with segfaults, where the kernel keeps
invoking the registered SIGSEGV handler, in these other cases the signal
needs to be re-enqueued before chaining to the next handler.
This is the case of abort(), which internally does a raise(SIGABRT).
BUG=437788
Review URL: https://codereview.chromium.org/769843002
Cr-Commit-Position: refs/heads/master@{#306179}
The WebView fingerprint crash handler introduced in crrev.com/678763005
was failing to cover the case of signals delivered through kill/raise.
Conversely to what happens with segfaults, where the kernel keeps
invoking the registered SIGSEGV handler, in these other cases the signal
needs to be re-enqueued before chaining to the next handler.
This is the case of abort(), which internally does a raise(SIGABRT).
BUG=437788
Review URL: https://codereview.chromium.org/769843002
Cr-Commit-Position: refs/heads/master@{#306179}
| android_webview/common/aw_crash_handler.cc | diffblobblamehistory |