Can We Make Sense of Android Crash Logs? Let’s Find Out

Too Long; Didn't Read

The Android Framework provides some great tools for debugging crashes. The Android framework provides several useful crash logs that developers can read. The three most important crash logs are exception stack traces, ANR traces, and NDK tombstones. These logs contain useful information about what went wrong in order to identify the cause of an app's failure to respond to user input for a noticeable period of time. The most common type of crash is an exception stack trace, which is logged out to Logcat. Tombstones are the closest to the metal in terms of information, as they record raw memory addresses.