I’m moving a project to the new Android Native Development Kit (i.e. JNI) and I’d like to catch SIGSEGV, should it occur (possibly also SIGILL, SIGABRT, SIGFPE) in order to present a nice crash reporting dialog, instead of (or before) what currently happens: the immediate unceremonious death of the process and possibly some attempt by the OS to restart it. (Edit: The JVM/Dalvik VM catches the signal and logs a stack trace and other useful information; I just want to offer the user the option to email that info to me really.)
The situation is: a large body of C code which I didn’t write does most of the work in this application (all the game logic) and although it’s well-tested on numerous other platforms, it’s entirely possible that I, in my Android port, will feed it garbage and cause a crash in native code, so I want the crash dumps (both native and Java) that currently show up in the Android log (I guess it would be stderr in a non-Android situation). I’m free to modify both C and Java code arbitrarily, although the callbacks (both going in and coming out of JNI) number about 40 and obviously, bonus points for small diffs.
I’ve heard of the signal chaining library in J2SE, libjsig.so, and if I could safely install a signal handler like that on Android, that would solve the catching part of my question, but I see no such library for Android/Dalvik.
Edit: From Jelly Bean onwards you can’t get the stack trace, because
READ_LOGS went away. 🙁
I actually got a signal handler working without doing anything too exotic, and have released code using it, which you can see on github (edit: linking to historical release; I removed the crash handler since then). Here’s how:
sigaction()to catch the signals and store the old handlers. (android.c:570)
- Time passes, a segfault happens.
- In the signal handler, call up to JNI one last time and then call the old handler. (android.c:528)
- In that JNI call, log any useful debugging info, and call
startActivity()on an activity that is flagged as needing to be in its own process. (SGTPuzzles.java:962, AndroidManifest.xml:28)
- When you come back from Java and call that old handler, the Android framework will connect to
debuggerdto log a nice native trace for you, and then the process will die. (debugger.c, debuggerd.c)
- Meanwhile, your crash-handling activity is starting up. Really you should pass it the PID so it can wait for step 5 to complete; I don’t do this. Here you apologise to the user and ask if you can send a log. If so, gather the output of
logcat -d -v threadtimeand launch an
ACTION_SENDwith recipient, subject and body filled in. The user will have to press Send. (CrashHandler.java, SGTPuzzles.java:462, strings.xml:41
- Watch out for
logcatfailing or taking more than a few seconds. I have encountered one device, the T-Mobile Pulse / Huawei U8220, where logcat immediately goes into the
T(traced) state and hangs. (CrashHandler.java:70, strings.xml:51)
In a non-Android situation, some of this would be different. You’d need to gather your own native trace, see this other question, depending on what sort of libc you have. You’d need to handle dumping that trace, launching your separate crash-handler process, and sending the email in some appropriate ways for your platform, but I imagine the general approach should still work.
I’m a little bit late, but I had the exact same need, and I’ve developed a small library to address it, by catching common crashes (
SIBGUS, etc.) inside JNI code, and replace them by regular
java.lang.Error exceptions. Bonus, if the client is running on Android >=
4.1.1, the stack trace embeds the resolved backtrace of the crash (a pseudo-trace containing the full native stack trace). You will not recover from vicious crashes (ie. if you corrupt the allocator, for example), but at least it should allows you to recover from most of them. (please report successes and failures, the code is brand new)
More info at https://github.com/xroche/coffeecatch
(code is BSD 2-Clauses license)
FWIW, Google Breakpad works fine on Android. I did the porting work, and we’re shipping it as part of Firefox Mobile. It requires a little setup, since it doesn’t give you stack traces on the client-side, but sends you the raw stack memory and does the stack walking server-side (so you don’t have to ship debug symbols with your app).
In my limited experience (non-Android), SIGSEGV in JNI code will generally crash the JVM before control is returned to your Java code. I vaguely recall hearing about some non-Sun JVM which lets you catch SIGSEGV, but AFAICR you can’t expect to be able to do so.
You can try to catch them in C (see sigaction(2)), although you can do very little after a SIGSEGV (or SIGFPE or SIGILL) handler as the ongoing behaviour of a process is officially undefined.