On 6/7/2012 5:34 AM, b0b wrote:
It *might* be possible to get that log , overriding the default
signal handlers in your NDK code and taking inspiration from
debuggerd.c which handle the logging of the detail trace (see
function handle_crashing_process):
debuggerd gets crash reports by reading the tombstone files from here:
#define TOMBSTONE_DIR "/data/tombstones"
Looking at my device with adb shell:
$ cd /data/tombstones
$ ls -l
ls -l
-rw------- system system 110833 2011-12-20 09:15 tombstone_03
-rw------- system system 74670 2011-11-02 07:51 tombstone_00
-rw------- system system 65631 2012-02-18 08:51 tombstone_05
-rw------- system system 83197 2012-01-06 14:13 tombstone_04
-rw------- system system 24404 2011-12-13 21:20 tombstone_02
-rw------- system system 84862 2012-05-23 17:47 tombstone_06
-rw------- system system 91046 2012-05-23 17:49 tombstone_07
-rw------- system system 65262 2011-11-05 19:40 tombstone_01
$
You'd need a rooted phone (or to be debuggerd) to read any of those
files. Thanks for the thought, but it won't work.
On the other end of things, I'm pretty certain that the code that
GENERATES the tombstone file (which is the place my app MIGHT be able to
do it as well) is going to need to use Linux APIs unsupported by the
NDK, which is its own can of worms.
Tim
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/android-discuss?hl=en.
