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:mimeType="text/XXX" cannot work on eclair

i have an activity whose intent-filter is android:mimeType="text/XXX"

so i select it on web pages , my activity will be launched
and before eclair it works well

but on eclair it fails

after checking

i found in

in function

it adds DOMImplementation::isTextMIMEType(mimeType) on eclair branch

so the webcore thinks it some kind of DOM so the mimeType cannot be
passed on

so i would like to ask why this check is added on eclair branch



2. Classification of Applications

The current classification or grouping of applications does not
consider the applications that are created by collaboration with
experts in the field in which the application supports.
The current market image of smart apps is they are free or cheap and
are not designed to improve ones life or health. One goes to the smart
app for the same reason one buys items from a flea market, or yard
You expect to get value for a cheap price at yard sales and flea
markets. The same mentality is evident on the Android market.
We need to create a classification of apps for those deemed created by
expert subject matter experts collaborating with expert technical
people to create an app that is useful in improving ones life and well
Change the market image for the smart app platform so these apps, that
are expensive to create, can participate above the noise of all the
free, almost free, or cheap apps.


3. Invoking apps in background when phone starts

4. app bound to its own virtual keyboard

5. problem with the fix Button at of the list View

6. localization

7. Stop Scroll In a WebView