| commit | c6a3e1753c19f49f8c1ea5896a456ee74601edec | [log] [tgz] |
|---|---|---|
| author | Mikhail Naganov <mnaganov@google.com> | Wed May 08 13:40:01 2024 -0700 |
| committer | Mikhail Naganov <mnaganov@google.com> | Wed May 08 16:34:36 2024 -0700 |
| tree | 1d3f42b8ca2bdf939d7eb5b42adbe450d0ccdc03 | |
| parent | f2dd4774b09a9b0b69193139bf4fbee85bbf640f [diff] |
Improve FMQ pointer corruption diagnostics Since sometimes an abort stack is the only information available, it is useful to have suspicious pointer values in the abort message. For that, it must be generated by the FMQ implementation itself as the client does not have access to the pointers. Because of that, change the parameter introduced by aosp/3073435 to an optional enum and an error string. Bug: 338974476 Test: m Change-Id: Ib9d61c787a9e1cd1197503aed698bc1e7e61bc87