diff options
| author | Andy McFadden <fadden@android.com> | 2011-10-13 16:05:08 -0700 |
|---|---|---|
| committer | Andy McFadden <fadden@android.com> | 2011-10-13 16:05:08 -0700 |
| commit | 41e0cef301637cd1f2daf72953d1230b7fb174b8 (patch) | |
| tree | 06ee3801e966f99682a80796d9b30060e128e5c9 /toolbox/Android.mk | |
| parent | 136dcc5ce628a1ba600a6818e5cb24d5f15eb016 (diff) | |
| download | system_core-41e0cef301637cd1f2daf72953d1230b7fb174b8.zip system_core-41e0cef301637cd1f2daf72953d1230b7fb174b8.tar.gz system_core-41e0cef301637cd1f2daf72953d1230b7fb174b8.tar.bz2 | |
Append log data to tombstones
The Android Problem Report site shows tombstones uploaded from
devices. We can see the native stack traces for every thread,
but sometimes there's a very important bit of information sitting
in the log, and without it we can't analyze the failure.
This change modifies debuggerd so that the log contents for the
crashing process are appended to the tombstone. The format matches
the output of "logcat -v threadtime". Both "system" and "main" logs
are included (but not interleaved -- we're not that fancy).
This feature is only enabled when the "ro.debuggable" system property
is set to 1 (indicating a development device).
Bug 5456676
Change-Id: I3be1df59813ccf1058cec496a906f6d31fbc7b04
Diffstat (limited to 'toolbox/Android.mk')
0 files changed, 0 insertions, 0 deletions