| commit | ed9ea9af2cf1ab10d0e5ecaaa008b19fe980a4aa | |
| author | pcc <pcc@chromium.org> | |
| Wed, 5 Aug 2015 00:46:39 +0000 (4 17:46 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Wed, 5 Aug 2015 00:47:56 +0000 (5 00:47 +0000) | ||
| tree | 9c2bb672074207e05303c9e8da9e1162547af0f5 | treesnapshot (tar.gz zip) |
| parent | d7d0894bef96ad7349d4089a0dc3a16c3b9c5e9f | commitdiff |
CFI: Enable stack traces in renderer process in non-official CFI builds.
A CFI failure causes a SIGILL signal to be raised, and the most likely
place for a failure to occur is in the renderer. By printing a stack trace
we provide developers with a basic set of information about CFI failures,
and allow crashes to be disambiguated by ClusterFuzz.
BUG=464797
R=jln@chromium.org,jam@chromium.org
Review URL: https://codereview.chromium.org/1269673003
Cr-Commit-Position: refs/heads/master@{#341833}
A CFI failure causes a SIGILL signal to be raised, and the most likely
place for a failure to occur is in the renderer. By printing a stack trace
we provide developers with a basic set of information about CFI failures,
and allow crashes to be disambiguated by ClusterFuzz.
BUG=464797
R=jln@chromium.org,jam@chromium.org
Review URL: https://codereview.chromium.org/1269673003
Cr-Commit-Position: refs/heads/master@{#341833}
| content/common/sandbox_linux/sandbox_linux.cc | diffblobblamehistory | |
| content/renderer/renderer_main.cc | diffblobblamehistory |