|author||Scott Graham <firstname.lastname@example.org>||Tue Nov 12 20:08:54 2019|
|committer||Commit Bot <email@example.com>||Wed Nov 13 00:26:24 2019|
fuchsia: Don't capture incorrect/unreasonably large stacks In a stack overflow test from the Fuchsia tree, an intentional crash was being induced that at the point it was reported to Crashpad resulted in a stack pointer outside of the stack. This caused two problems: - Crashpad attempted to capture that whole "thing" which could have been anything, and in the failing test was a 1G guard region - The whole wrong thing could be very large, resulting in OOM when trying to write the minidump, which was the symptom of the bug. Don't attempt to continue of SP isn't at least in a mapping, and don't capture too-large regions for the stack as nothing useful can come of that anyway. New test added: ProcessSnapshotFuchsiaTest.InvalidStackPointer. Bug: fuchsia:41212 Change-Id: Ifb48fd8b4b5b2f0cf10ab97e01dbd8b842368775 Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/1912942 Commit-Queue: Scott Graham <firstname.lastname@example.org> Reviewed-by: Francois Rousseau <email@example.com>
Crashpad is a crash-reporting system.
Crashpad’s source code is hosted in a Git repository at https://chromium.googlesource.com/crashpad/crashpad.