DOMINIK SYMONOWICZ's blog - FOREVER HUNGRY of knowledge , sarcasm , smiling , music , dancing , and food ...lots of food.
This blog is as notes with solutions for simple problems that happen to graduate developer.
Instead of copy and paste solutions from website and add my nickname ... I tried give simplified solution with explanation , added documentation , sarcastic comment and weird example.
I hope you will enjoying reading.
STORY: I updated my Doms diagnostic tool recently, so I went to Developer Console few times to see is everything works smoothly. Unfortunately I saw 1 crash Native crash in unknown.unknown (Report can be found on the end ). Information looks useless, but if this happen to you, then follow this slides(By Ashish Agrawal ,who works for Motorola Mobility): http://www.slideshare.net/AshishAgrawal22/android-crash-debugging-15694310 It will help you how to read report and where to looks for hint where more-less shit hit the fan. In my case: From report,following lines gives me few clues
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr ede811cc
#01 pc 00019557 /system/lib/libmedia_jni.so (android::sp<android::MediaRecorder>::sp(android::MediaRecorder*)
Crash happen on modern Samsung GT-I9500 on Android 4.3(SDK: 18). It means well-known manufacturer and decent version of Android. It means random error, problem with specific device ,Android bug or my app do weird thing
It was caused by access violation
I use MediaRecorder in one place and I have done some changes recently.
WHAT TO DO:
Figure out is device is well-known (as if it happens on odd and unknown manufacture it usually means with device problem,not your application)
Check,what type of error is it (ANR, android exception, your exception, thread problem,caused by your app's thread or other, etc.)
Which android component was involved in crash(in my case MediaRecorder )
Search on internet for problems :)\
Ignore problem ,if occurred once,but if appear more often,then ... fight to the end or rollback recent changes. (if problem affect specific device ,then add them to not-compatible devices on Development Console).
CONCLUSION: I know,where more-less problem occurred, I don't know why, how to reproduce and how to solve it. I hope, it will help you to decode mysterious 'Native crash in unknown.unknown' error and narrow your finding where bug could occurred. Resources: Slides by Ashish Agrawal - http://www.slideshare.net/AshishAgrawal22/android-crash-debugging-15694310