diff options
| author | Andreas Gampe <agampe@google.com> | 2019-07-08 08:31:27 -0700 |
|---|---|---|
| committer | Andreas Gampe <agampe@google.com> | 2019-07-10 15:22:14 -0700 |
| commit | 9ff9c40113244b9dce0a3c3b1a4ba677a60ae3cb (patch) | |
| tree | 5577bec32f7bc511569278ede94f1f5dc5130fa0 /tools/dump-coverage/dump_coverage.cc | |
| parent | 79a2b5215d363cd7ea80660c5f27cefceec92426 (diff) | |
Framework: Improve binder Error logging
In protracted cases, diagnostic code cannot retrieve any Java-side
data. Add two specific cases and instanceof checks (which require
no allocation etc), and a special message, so that aborts have
meaningful data (in case logcat is missing).
Sample:
Abort message: 'JNI FatalError called: java.lang.Error thrown during binder transaction: (Unknown exception message) (Error was OutOfMemoryError) (toString() error was OutOfMemoryError)'
Bug: 136482507
Test: m
Test: manual
Change-Id: I5c0c1d74ba8a6aeafee95b578a422a80b9899196
Diffstat (limited to 'tools/dump-coverage/dump_coverage.cc')
0 files changed, 0 insertions, 0 deletions