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. Developers Count on Android v's iPhone?

Anyone out there that can tell us the count of developer-members for
iPhone?  Is this info available from any of you iphone developers?

On Android its :

2. Starting an instrumentation with an intent

Hello all,
I am trying to test my activities. I have been using
ActivityInstrumentationTestCase however, I can not see any way to
start the activity with an intent. From what I understand the activity
is started in the setup() via super.launchActivity(pkg, activityCls,
extras). Is there any way to set the intent before starting the

The reason I am asking is because I have the following in my onCreate
in the activity:

                if (intent.getData() == null) {
                        Log.e(TAG, "Can not display single route without a 
                } else {
                        Cursor cursor = managedQuery(intent.getData(), 
null, null);

As you can see, without the intent'data , I can not start the

Any comments are much appreciated.


3. How & When we use "KeyguardLock" or "KeyguardManager"

4. Activities Refactoring

5. Keyboard confusion

6. I want to know a button's width before it is drawn on the screen! possible?

7. SAXParser reports different name on SDK 0.9 from SDK 1.0