Android: is there a way to dump crash logs locally on test device with no computer connected

Artie Vandelay 0
Viewed 29

I'm experiencing pesky SIGSEGV faults in my Android app. They are inconsistent to reproduce and mostly happen after my app has been restarted a couple of times. The problem is, when the app restarts, Android Studio stops showing the logs, making it very hard for me to figure out what the issue is. When I restart the app using the Android Studio restart button, it loads a fresh install of the app onto my phone, which is an issue because the errors don't seem to happen on very fresh installs.

My question is: can I somehow have Android Studio still show the live logs WITHOUT reinstalling the app every time, OR can I run the app without being connected to any PC, and dump a crash log file locally to the phone when the app crashes, so that I can open the logs later on?

crash segmentation-fault android-studio android
1 Answers

Filtering logcat

The problem is, when the app restarts, Android Studio stops showing the logs, making it very hard for me to figure out what the issue is.

It sounds like the logcat in android studio is filtering by application. You can change it to no filter and set the text filter to your application's id. This way the logcat will not be cleared once the application process dies/restarts.

Extracting the tombstones

Since this is an Android native crash it will not be sent to bug capturing software such as Crashlytics or Bugfender etc.. you can pull the tombstone[s] directly from the device with adb.

adb bugreport bugreport.zip

Once extracted, the tombstones will be under path /bugreport/FS/data/tombstones/.

Typically 10 tombstones will get saved to device storage but will get overwritten by earlier native crashes once the limit to the number of retained tombstones has been met.

Android documentation: Using bugreport

Android documentation: Debugging tombstones

JakeB0
Related