Does Application Error Reports support crashes in native code?

by Shri » Fri, 20 May 2011 02:15:51 GMT

Sponsored Links
 Does the Application Error Reports infrastructure described at 
work for crashes in native code?

It sounds like the mechanism works by using
Thread.setDefaultUnhandledExceptionHandler which only works for Java
code, and so it will not work for native code. Are there any solutions
for native code? I am working on registering a signal handler which
starts a separate process (since crashes in native code can leave the
process in a bad state) to get the logcat logs and then send those.
Just wondering if there is any better solution.


Other Threads

1. Android statistics

With the new Developer Console stats, I can finally get some useful

I was thinking of dumping support for Android 1.5, however, according
to the dev console stats, 11.5% of my users are still on 1.5!

I can only assume the number is so high because these users don't have
many other apps to choose from?

In any case, I'll be keeping support for 1.5.

Anyone else notice anything interesting?


2. Data Access process in Android


I know that every application in Android runs in a separate Dalvik VM
and has its personal storage space. It stores the data in this storage
space and no other application (except those with same UID) can
interfere with that data. AFAIK this process (Sandboxing) is done by
the Linux kernel. Is Android framework involved in this process

Thanks in advance.


3. progressbar spin counterclockwise?

4. VP8 Codec Support GB Capabilities

5. [WTShare]Ant Mayhem

6. native android opengl application

7. [WTS] GadgetGaya Clearance Sale, Up to 50% Off