I am building an app where part of it is built in JNI. The app crashes
and prints out the following stack dump within LogCat.

The question is what tool can I use to analyze the stack dump. Is
there a documented procedures somewhere. For example, how can I
generate the map file to reconcile the PC address with the code?


05-20 06:19:01.772: INFO/DEBUG(959): *** *** *** *** *** *** *** ***
*** *** *** *** *** *** *** ***
05-20 06:19:01.772: INFO/DEBUG(959): Build fingerprint: 'generic/sdk/
generic/:1.5/CUPCAKE/147336:eng/test-keys'
05-20 06:19:01.772: INFO/DEBUG(959): pid: 3775, tid: 3775  >>>
com.mycompany.android.app <<<
05-20 06:19:01.772: INFO/DEBUG(959): signal 11 (SIGSEGV), fault addr
00000000
05-20 06:19:01.772: INFO/DEBUG(959):  r0 00000021  r1 00000000  r2
00195bf8  r3 8049279c
05-20 06:19:01.772: INFO/DEBUG(959):  r4 804a8270  r5 00000000  r6
804aefd4  r7 00000684
05-20 06:19:01.772: INFO/DEBUG(959):  r8 000002f8  r9 41049db8  10
41049da4  fp 00000000
05-20 06:19:01.772: INFO/DEBUG(959):  ip afbc30c8  sp bec524e8  lr
afbc1123  pc 804927a4  cpsr 60000010
05-20 06:19:02.089: INFO/DEBUG(959):          #00  pc 000927a4  /data/
data/com.mycompany.android.app/lib/libMyLib.so
05-20 06:19:02.089: INFO/DEBUG(959):          #01  pc 00092ab0  /data/
data/com.mycompany.android.app/lib/libMyLib.so
05-20 06:19:02.099: INFO/DEBUG(959):          #02  pc 0009df60  /data/
data/com.mycompany.android.app/lib/libMyLib.so
05-20 06:19:02.099: INFO/DEBUG(959):          #03  pc 0009e45c  /data/
data/com.mycompany.android.app/lib/libMyLib.so
05-20 06:19:02.099: INFO/DEBUG(959):          #04  pc 00027e90  /data/
data/com.mycompany.android.app/lib/libMyLib.so
05-20 06:19:02.119: INFO/DEBUG(959):          #05  pc 00028fcc  /data/
data/com.mycompany.android.app/lib/libMyLib.so
05-20 06:19:02.119: INFO/DEBUG(959):          #06  pc 000296a8  /data/
data/com.mycompany.android.app/lib/libMyLib.so
05-20 06:19:02.129: INFO/DEBUG(959):          #07  pc 0000e3b4  /
system/lib/libdvm.so
05-20 06:19:02.129: INFO/DEBUG(959):          #08  pc 00040a8a  /
system/lib/libdvm.so
05-20 06:19:02.149: INFO/DEBUG(959):          #09  pc 00013118  /
system/lib/libdvm.so
05-20 06:19:02.149: INFO/DEBUG(959):          #10  pc 00017b1c  /
system/lib/libdvm.so
05-20 06:19:02.159: INFO/DEBUG(959):          #11  pc 00017560  /
system/lib/libdvm.so
05-20 06:19:02.159: INFO/DEBUG(959):          #12  pc 00052268  /
system/lib/libdvm.so
05-20 06:19:02.179: INFO/DEBUG(959):          #13  pc 000596ee  /
system/lib/libdvm.so
05-20 06:19:02.179: INFO/DEBUG(959):          #14  pc 00013118  /
system/lib/libdvm.so
05-20 06:19:02.189: INFO/DEBUG(959):          #15  pc 00017b1c  /
system/lib/libdvm.so
05-20 06:19:02.189: INFO/DEBUG(959):          #16  pc 00017560  /
system/lib/libdvm.so
05-20 06:19:02.199: INFO/DEBUG(959):          #17  pc 000520ec  /
system/lib/libdvm.so
05-20 06:19:02.209: INFO/DEBUG(959):          #18  pc 0003f0f8  /
system/lib/libdvm.so
05-20 06:19:02.219: INFO/DEBUG(959):          #19  pc 00031ac2  /
system/lib/libdvm.so
05-20 06:19:02.229: INFO/DEBUG(959):          #20  pc 00028280  /
system/lib/libandroid_runtime.so
05-20 06:19:02.229: INFO/DEBUG(959):          #21  pc 00028d7e  /
system/lib/libandroid_runtime.so
05-20 06:19:02.259: INFO/DEBUG(959):          #22  pc 00008bf2  /
system/bin/app_process
05-20 06:19:02.309: INFO/DEBUG(959):          #23  pc 0001fd22  /
system/lib/libc.so
05-20 06:19:02.309: INFO/DEBUG(959):          #24  pc 0000bcb2  /
system/lib/libc.so
05-20 06:19:02.428: INFO/DEBUG(959):          #25  pc b000157e  /
system/bin/linker
05-20 06:19:02.428: INFO/DEBUG(959): stack:
05-20 06:19:02.428: INFO/DEBUG(959):     bec524a8  804aed10
05-20 06:19:02.428: INFO/DEBUG(959):     bec524ac  804aed24
05-20 06:19:02.428: INFO/DEBUG(959):     bec524b0  804aefd4
05-20 06:19:02.428: INFO/DEBUG(959):     bec524b4  3120035d
05-20 06:19:02.428: INFO/DEBUG(959):     bec524b8  804a8270
05-20 06:19:02.428: INFO/DEBUG(959):     bec524bc  804a8270
05-20 06:19:02.428: INFO/DEBUG(959):     bec524c0  001ac810  [heap]
05-20 06:19:02.428: INFO/DEBUG(959):     bec524c4  3120035d
05-20 06:19:02.428: INFO/DEBUG(959):     bec524c8  00000684
05-20 06:19:02.428: INFO/DEBUG(959):     bec524cc  804a8270
05-20 06:19:02.428: INFO/DEBUG(959):     bec524d0  00000000
05-20 06:19:02.428: INFO/DEBUG(959):     bec524d4  804aefd4
05-20 06:19:02.428: INFO/DEBUG(959):     bec524d8  00000684
05-20 06:19:02.428: INFO/DEBUG(959):     bec524dc  8049279c  /data/
data/com.mycompany.android.app/lib/libMyLib.so
05-20 06:19:02.428: INFO/DEBUG(959):     bec524e0  df002777
05-20 06:19:02.428: INFO/DEBUG(959):     bec524e4  e3a070ad
05-20 06:19:02.428: INFO/DEBUG(959): #00 bec524e8  8049f650  /data/
data/com.mycompany.android.app/lib/libMyLib.so
05-20 06:19:02.428: INFO/DEBUG(959):     bec524ec  804aefd4
05-20 06:19:02.428: INFO/DEBUG(959):     bec524f0  804a8270
05-20 06:19:02.428: INFO/DEBUG(959):     bec524f4  001aaee8  [heap]
05-20 06:19:02.428: INFO/DEBUG(959):     bec524f8  00000684
05-20 06:19:02.428: INFO/DEBUG(959):     bec524fc  80492ab4  /data/
data/com.mycompany.android.app/lib/libMyLib.so
05-20 06:19:02.428: INFO/DEBUG(959): #01 bec52500  00195390  [heap]
05-20 06:19:02.428: INFO/DEBUG(959):     bec52504  00000914
05-20 06:19:02.428: INFO/DEBUG(959):     bec52508  804a8270
05-20 06:19:02.428: INFO/DEBUG(959):     bec5250c  00000748
05-20 06:19:02.428: INFO/DEBUG(959):     bec52510  bec52550  [stack]
05-20 06:19:02.428: INFO/DEBUG(959):     bec52514  8049df64  /data/
data/com.mycompany.android.app/lib/libMyLib.so
05-20 06:19:03.378: INFO/ActivityManager(567): Process
com.mycompany.android.app (pid 3775) has died.

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to