diff options
| author | 2023-03-20 14:43:23 -0700 | |
|---|---|---|
| committer | 2023-03-23 07:17:17 -0700 | |
| commit | 1126a08dd823c95a73dbad7b3491605b3c9cbc64 (patch) | |
| tree | 5b9302f27364850f652de1ab32d9e872e5967dca /api/api.go | |
| parent | 627b64593d21973e09dd64a46fd7ecc902390e83 (diff) | |
New ActivityManager<->debuggerd protocol for recoverable crashes.
Recoverable GWP-ASan catches memory safety bugs, prints debuggerd
reports, but then is able to patch up the process so that a crash
doesn't have to occur. Currently, because AM receives an IPC from
debuggerd, this results in the app being killed.
We previously worked around this by just making debuggerd not send an
IPC for GWP-ASan crashes, but this was overzealous and resulted in the
debuggerd crash not finding its way to dropbox.
So, to handle this, we introduce a new API between debuggerd and
ActivityManager.
For recoverable crashes, introduce a new log tag and extend other stats
logging areas to also add fields to indicate the crash was recoverable.
Readers of these fields should assume that, if the recoverable field is
set, the app didn't actually crash but the app had a recoverable memory
safety violation.
The GWP-ASan CTS additions (in this topic) cover the behaviour and
ensure that the recoverable crashes make their way to dropbox.
Bug: 270720163
Test: atest CtsGwpAsanTestCases
Change-Id: If3515d30a8dcacd9434b30751ae735b050d88e7d
Diffstat (limited to 'api/api.go')
0 files changed, 0 insertions, 0 deletions