1

When I encounter a native code crash, the backtrace in LogCat has only the top most two frame, I can't see other frames, which makes debugging quite frustrating. Is there any way I can see more stack trace frames in LogCat?

CarmeloS
  • 7,868
  • 8
  • 56
  • 103
  • What are the frames? What version of Android? I've had issues in the past with functions marked "noreturn" because they don't have to preserve the link register. – fadden Jul 22 '14 at 15:53
  • @fadden frames are the list of function calling chain, you can take Android 4.2 in specific, but I see most Android version has this problem. – CarmeloS Jul 24 '14 at 10:27
  • I'm asking what are the functions shown in the frames, i.e. do you see `abort` or `_div0` or is it code from your library? – fadden Jul 24 '14 at 15:39
  • @fadden sorry I'v misunderstood you, those frames are normal frames which are exactly my functions. – CarmeloS Jul 25 '14 at 02:11

1 Answers1

0

You can go for gdb for native application debuging on android Generate core dump in android hope this will provide even more info. I got this incomplete backtrace in logcat here. Refer here for more http://mhandroid.wordpress.com/2011/01/23/using-eclipse-for-android-cc-debugging/ Hope I got your question right.

Community
  • 1
  • 1
MOSO
  • 393
  • 2
  • 9
  • Although debugging is a way to solve this, I need the stack trace in the log so that if user crashes, I can get a report of the crash stack trace. – CarmeloS Jul 22 '14 at 11:57