Decoding crash dump to get stack trace
Christopher Van Kirk
It seems like once upon a time there was a utility that enabled one to
parse a native code crash dump (like the one attached). It used to be
here: http://pdk.android.com/online-pdk/guide/debugging_gdb.html but
that link is now dead with no onward reference. Could anyone point me to
some method to get a stack trace from a dump like the one below?
Cheers,
Chris...
10-12 22:16:14.130: INFO/DEBUG(2586): *** *** *** *** *** *** *** ***
*** *** *** *** *** *** *** ***
10-12 22:16:14.130: INFO/DEBUG(2586): Build fingerprint:
'samsung/GT-I9100/GT-I9100:2.3.3/GINGERBREAD/XWKF1:user/release-keys'
10-12 22:16:14.130: INFO/DEBUG(2586): pid: 4410, tid: 4528 >>> com.game <<<
10-12 22:16:14.130: INFO/DEBUG(2586): signal 11 (SIGSEGV), code 1
(SEGV_MAPERR), fault addr 0e000122
10-12 22:16:14.130: INFO/DEBUG(2586): r0 0e00010e r1 47ea5954 r2
0e00010e r3 0e00010e
10-12 22:16:14.130: INFO/DEBUG(2586): r4 00210c40 r5 00210c10 r6
3f800000 r7 00222e38
10-12 22:16:14.130: INFO/DEBUG(2586): r8 001413d8 r9 46ee5ed8 10
fffffe84 fp 4449f31c
10-12 22:16:14.130: INFO/DEBUG(2586): ip 80000000 sp 47ea56a8 lr
814ac737 pc 8149af66 cpsr 00000030
10-12 22:16:14.130: INFO/DEBUG(2586): d0 1000004000000000 d1
1000004100000003
10-12 22:16:14.130: INFO/DEBUG(2586): d2 1000010f3f800000 d3
1000010e00000000
10-12 22:16:14.130: INFO/DEBUG(2586): d4 0000000041ff1eb8 d5
3f80000000000000
10-12 22:16:14.130: INFO/DEBUG(2586): d6 000001e03f800000 d7
0000000044480000
10-12 22:16:14.130: INFO/DEBUG(2586): d8 40df248000000000 d9
0000000000000000
10-12 22:16:14.130: INFO/DEBUG(2586): d10 0000000000000000 d11
0000000000000000
10-12 22:16:14.130: INFO/DEBUG(2586): d12 0000000000000000 d13
0000000000000000
10-12 22:16:14.130: INFO/DEBUG(2586): d14 0000000000000000 d15
0000000000000000
10-12 22:16:14.135: INFO/DEBUG(2586): d16 000000c24056b2d8 d17
3f50624dd2f1a9fc
10-12 22:16:14.135: INFO/DEBUG(2586): d18 bf2a00db7bac2b85 d19
3ec6cd878c3b46a7
10-12 22:16:14.135: INFO/DEBUG(2586): d20 3f08a1e5c6d3098d d21
3ebc714e1f1f132e
10-12 22:16:14.135: INFO/DEBUG(2586): d22 3ff0000000000000 d23
3fe9216610c8da46
10-12 22:16:14.135: INFO/DEBUG(2586): d24 3e66376972bea4d0 d25
0000000000000000
10-12 22:16:14.135: INFO/DEBUG(2586): d26 0000000000000000 d27
3ef99342e0ee5069
10-12 22:16:14.135: INFO/DEBUG(2586): d28 000f000100000000 d29
3ff0000000000000
10-12 22:16:14.135: INFO/DEBUG(2586): d30 0000000000000000 d31
3ff0000000000000
10-12 22:16:14.135: INFO/DEBUG(2586): scr 80000011
10-12 22:16:14.295: INFO/DEBUG(2586): #00 pc 0009af66
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.295: INFO/DEBUG(2586): #01 pc 000ac732
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.295: INFO/DEBUG(2586): #02 pc 000ab95c
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.295: INFO/DEBUG(2586): #03 pc 000ccf1e
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.295: INFO/DEBUG(2586): #04 pc 000cd9be
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.295: INFO/DEBUG(2586): #05 pc 000cc91c
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.295: INFO/DEBUG(2586): #06 pc 000cbc64
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.295: INFO/DEBUG(2586): #07 pc 000cb4fc
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.300: INFO/DEBUG(2586): #08 pc 000cb71a
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.300: INFO/DEBUG(2586): #09 pc 000a2982
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.300: INFO/DEBUG(2586): #10 pc 000a302c
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.300: INFO/DEBUG(2586): #11 pc 0009e508
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.300: INFO/DEBUG(2586): #12 pc 0009e758
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.300: INFO/DEBUG(2586): #13 pc 0009a696
/data/data/com.game/lib/libGAME.so
10-12 22:16:14.300: INFO/DEBUG(2586): #14 pc 00017e74
/system/lib/libdvm.so
10-12 22:16:14.300: INFO/DEBUG(2586): code around pc:
10-12 22:16:14.300: INFO/DEBUG(2586): 8149af44 9b00605a 9b01681a
9b00609a 9b01681a
10-12 22:16:14.300: INFO/DEBUG(2586): 8149af54 9b0160da b0021c18
46c04770 9001b082
10-12 22:16:14.300: INFO/DEBUG(2586): 8149af64 695b9b01 b0021c18
46c04770 b083b500
10-12 22:16:14.300: INFO/DEBUG(2586): 8149af74 9b019001 f0001c18
1c03f877 23011c1a
10-12 22:16:14.300: INFO/DEBUG(2586): 8149af84 061b4053 2b000e1b
9b01d005 2b00695b
10-12 22:16:14.300: INFO/DEBUG(2586): code around lr:
10-12 22:16:14.300: INFO/DEBUG(2586): 814ac714 e0012300 425b2301
9b05e000 b0091c18
10-12 22:16:14.300: INFO/DEBUG(2586): 814ac724 46c0bd00 b083b500
9b019001 f7ee1c18
10-12 22:16:14.305: INFO/DEBUG(2586): 814ac734 1c03fc15 b0031c18
46c0bd00 b083b500
10-12 22:16:14.305: INFO/DEBUG(2586): 814ac744 9b019001 f7ee1c18
1c03fc61 b0031c18
10-12 22:16:14.305: INFO/DEBUG(2586): 814ac754 46c0bd00 b085b500
91029003 9a039201
10-12 22:16:14.305: INFO/DEBUG(2586): stack:
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea5668 00000000
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea566c 00179408
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea5670 00000000
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea5674 00000000
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea5678 003b0170
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea567c 0016eca8
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea5680 00001008
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea5684 0043f4b0
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea5688 00213b64
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea568c 00213b58
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea5690 00141d88
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea5694 00141da0
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea5698 00141d98
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea569c afd14163
/system/lib/libc.so
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea56a0 df002777
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea56a4 e3a070ad
10-12 22:16:14.305: INFO/DEBUG(2586): #00 47ea56a8 00000808
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea56ac 0e00010e
10-12 22:16:14.305: INFO/DEBUG(2586): #01 47ea56b0 001e7324
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea56b4 0e00010e
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea56b8 00213b64
10-12 22:16:14.305: INFO/DEBUG(2586): 47ea56bc 814ab961
/data/data/com.game/lib/libGAME.so
David Turner
Hi there.
It seems like once upon a time there was a utility that enabled one to parse a native code crash dump (like the one attached). It used to be here: http://pdk.android.com/online-pdk/guide/debugging_gdb.html but that link is now dead with no onward reference. Could anyone point me to some method to get a stack trace from a dump like the one below?
--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-ndk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-ndk?hl=en.
Christopher Van Kirk
On 10/12/2011 10:40 PM, David Turner wrote:
On Wed, Oct 12, 2011 at 4:28 PM, Christopher Van Kirk <christoph...@gmail.com> wrote:
Hi there.
It seems like once upon a time there was a utility that enabled one to parse a native code crash dump (like the one attached). It used to be here: http://pdk.android.com/online-pdk/guide/debugging_gdb.html but that link is now dead with no onward reference. Could anyone point me to some method to get a stack trace from a dump like the one below?
I invite you to download the latest NDK release, then read docs/NDK-STACK.html :-)
Only...
When I ran the utility it gave me back something like this:
********** Crash dump: **********
Build fingerprint: 'samsung/GT-I9100/GT-I9100:2.3.3/GINGERBREAD/XWKF1:user/release-keys'
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 43960024
Stack frame #00 pc 000b4746 /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #01 pc 000c5f12 /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #02 pc 000c513c /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #03 pc 000e66fe /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #04 pc 000e719e /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #05 pc 000e60fc /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #06 pc 000e5444 /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #07 pc 000e4cdc /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #08 pc 000e4efa /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #09 pc 000bc092 /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #10 pc 000bc80c /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #11 pc 000b7ce8 /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #12 pc 000b7f38 /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #13 pc 000b3e76 /data/data/com.company.games.game/lib/libgame.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libgame.so. Error (3): No such process
Stack frame #14 pc 00017e74 /system/lib/libdvm.so: Unable to open symbol file /cygdrive/c/projects/vankirkc/Android/game/obj/local/armeabi/libdvm.so. Error (3): No such process
Would this be due to missing debug information, and if so, how might I add that in?
Cheers again!
Chris...
David Turner
--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-ndk...@googlegroups.com.
Christopher Van Kirk
Winson Ho
I am also interested in this subject. I try to find NDK-STACK.html in my NDK r5c inside Nesessitas 0.2.1, but I can not find it.
My question is, does it comes with latest NDK release (NDK r6b?) only?
And can I use it on my NDK r5c?
I will try it anyway. If you know the answers, please help.
Thanks a lot.
Best regards,
Winson Ho.
David Turner
Hi All,
I am also interested in this subject. I try to find NDK-STACK.html in my NDK r5c inside Nesessitas 0.2.1, but I can not find it.
My question is, does it comes with latest NDK release (NDK r6b?) only?
And can I use it on my NDK r5c?
I will try it anyway. If you know the answers, please help.
Thanks a lot.
Winson Ho
Thanks for your reply.
I am trying it now.
Winson.