获得调用堆栈函数名 [英] Get function names from call stack
问题描述
我工作的一个Android程序,它调用原生code。这本地code为段错误,并且由于越来越调试通过Android NDK的工作是不是真的可行,我留下了类似如下(从DDMS捕获)调用堆栈。我的问题是,是否有什么东西我可以在事后手动运行在调用堆栈的功能名称内存地址转换,所以我可以看到这是段错误。
感谢
02-22 14:47:39.231:DEBUG / dalvikvm(504):试图加载的lib /data/data/android.TestApp/lib/libDM.so 0x43b7c938
02-22 14:47:39.301:DEBUG / dalvikvm(504):加入LIB /data/data/android.TestApp/lib/libDM.so 0x43b7c938共享
02-22 14:47:39.310:DEBUG / dalvikvm(504):无JNI_OnLoad在/data/data/android.TestApp/lib/libDM.so 0x43b7c938发现
02-22 14:47:39.406:DEBUG / dalvikvm(504):+++不扫描/system/lib/libwebcore.so'为'onLoadModel(错误CL)
02-22 14:47:39.410:DEBUG / dalvikvm(504):+++不扫描/system/lib/libmedia_jni.so'为'onLoadModel(错误CL)
02-22 14:47:39.410:DEBUG / dalvikvm(504):+++不扫描/system/lib/libexif.so'为'onLoadModel(错误CL)
02-22 14:47:39.410:DEBUG / dalvikvm(504):+++不扫描/system/lib/libsrec_jni.so'为'onLoadModel(错误CL)
02-22 14:47:39.569:信息/ DEBUG(28):*** *** *** *** *** *** *** *** *** *** *** * ** *** *** *** ***
02-22 14:47:39.569:信息/ DEBUG(28):构建指纹:通用/ SDK /通用/ 2.1 / ERD79 / 22607:主机/测试键
02-22 14:47:39.569:信息/ DEBUG(28):PID:504,TID:504>>> android.TestApp<<<
02-22 14:47:39.569:信息/ DEBUG(28):11(SIGSEGV),故障地址00000008
02-22 14:47:39.581:信息/ DEBUG(28):R0,R1 00000000 00000068 00002350 R2 R3 80facc00
02-22 14:47:39.581:信息/ DEBUG(28):R4 beb3c918 R5 000024b8 R6 fffacafc R7 0000aa98
02-22 14:47:39.581:信息/ DEBUG(28):R8 00000000 R9 000024b8 10 fffacafc FP 00000000
02-22 14:47:39.581:信息/ DEBUG(28):IP afbc30c8 SP beb3c858 LR 80dffdf3 PC 80dfb18a CPSR 40000030
02-22 14:47:39.711:信息/ DEBUG(28):00#PC 001fb18a /data/data/android.TestApp/lib/libDM.so
02-22 14:47:39.733:信息/ DEBUG(28):#01件001ffdee /data/data/android.TestApp/lib/libDM.so
02-22 14:47:39.740:信息/ DEBUG(28):#02件0031cc2c /data/data/android.TestApp/lib/libDM.so
02-22 14:47:39.754:信息/ DEBUG(28):#03件0031cd74 /data/data/android.TestApp/lib/libDM.so
02-22 14:47:39.761:信息/ DEBUG(28):#04件0000f1f4 /system/lib/libdvm.so
02-22 14:47:39.769:信息/ DEBUG(28):05#PC 00038018 /system/lib/libdvm.so
02-22 14:47:39.779:信息/ DEBUG(28):#06件000316a2 /system/lib/libdvm.so
02-22 14:47:39.790:信息/ DEBUG(28):07#PC 0003d31c /system/lib/libdvm.so
02-22 14:47:39.810:信息/ DEBUG(28):08#PC 00013f58 /system/lib/libdvm.so
02-22 14:47:39.810:信息/ DEBUG(28):09#PC 00019888 /system/lib/libdvm.so
02-22 14:47:39.820:信息/ DEBUG(28):#10件00018d5c /system/lib/libdvm.so
02-22 14:47:39.846:信息/ DEBUG(28):11#PC 0004d3bc /system/lib/libdvm.so
02-22 14:47:39.852:信息/ DEBUG(28):12#PC 00054e74 /system/lib/libdvm.so
02-22 14:47:39.871:信息/ DEBUG(28):13#PC 00013f58 /system/lib/libdvm.so
02-22 14:47:39.871:信息/ DEBUG(28):14#PC 00019888 /system/lib/libdvm.so
02-22 14:47:39.889:信息/ DEBUG(28):#15件00018d5c /system/lib/libdvm.so
02-22 14:47:39.889:信息/ DEBUG(28):16#PC 0004d6d0 /system/lib/libdvm.so
02-22 14:47:39.900:信息/ DEBUG(28):17#PC 0003a72c /system/lib/libdvm.so
02-22 14:47:39.909:信息/ DEBUG(28):18#PC 0002be52 /system/lib/libdvm.so
02-22 14:47:39.921:信息/ DEBUG(28):19#PC 00026cf4 /system/lib/libandroid_runtime.so
02-22 14:47:39.930:信息/ DEBUG(28):#20件000279d8 /system/lib/libandroid_runtime.so
02-22 14:47:39.940:信息/ DEBUG(28):21#PC 00008cae /系统/斌/ app_process
02-22 14:47:39.949:信息/ DEBUG(28):22#PC 0000c2c6 /system/lib/libc.so
02-22 14:47:39.969:信息/ DEBUG(28):23#PC b00018aa /系统/斌/连接器
02-22 14:47:39.981:信息/ DEBUG(28):code左右邮编:
02-22 14:47:39.981:信息/ DEBUG(28):80dfb178 fffaaac8 4656b570 4644464d 4680b470
02-22 14:47:39.981:信息/ DEBUG(28):80dfb188 6883b081 1c0d1c08 22b04798 46814442
02-22 14:47:39.981:信息/ DEBUG(28):80dfb198 46921c10 f73d2600 4642ea90 6c546c13
02-22 14:47:39.981:信息/ DEBUG(28):code左右LR:
02-22 14:47:39.981:信息/ DEBUG(28):80dffde0 1c064a0b 589b447b 681c1c31 f7fb1c20
02-22 14:47:39.981:信息/ DEBUG(28):80dffdf0 1c05f9c5 d0062800 d0042c00 23001c32
02-22 14:47:39.981:信息/ DEBUG(28):80dffe00 f7fb1c20 1c28fa15 0000bd70 001a47f8
02-22 14:47:39.981:信息/ DEBUG(28):堆栈:
02-22 14:47:39.981:信息/ DEBUG(28):beb3c818 afe42ad4
02-22 14:47:39.981:信息/ DEBUG(28):beb3c81c ad07ff50 /system/lib/libdvm.so
02-22 14:47:39.990:信息/ DEBUG(28):beb3c820 0000bd00 [堆]
02-22 14:47:39.990:信息/ DEBUG(28):beb3c824 00000000
02-22 14:47:39.990:信息/ DEBUG(28):beb3c828 00085920 [堆]
02-22 14:47:40.000:信息/ DEBUG(28):beb3c82c 00000000
02-22 14:47:40.000:信息/ DEBUG(28):beb3c830 FFFFFFFF
02-22 14:47:40.000:信息/ DEBUG(28):beb3c834 beb3c850 [堆栈]
02-22 14:47:40.015:信息/ DEBUG(28):beb3c838 00000000
02-22 14:47:40.015:信息/ DEBUG(28):beb3c83c 00000000
02-22 14:47:40.022:信息/ DEBUG(28):beb3c840 ad563b21 /system/lib/libicuuc.so
02-22 14:47:40.022:信息/ DEBUG(28):beb3c844 00085968 [堆]
02-22 14:47:40.030:信息/ DEBUG(28):beb3c848 00000001
02-22 14:47:40.050:信息/ DEBUG(28):beb3c84c 00000000
02-22 14:47:40.061:信息/ DEBUG(28):beb3c850 df002777
02-22 14:47:40.061:信息/ DEBUG(28):beb3c854 e3a070ad
02-22 14:47:40.070:信息/ DEBUG(28):#00 beb3c858 ad065714 /system/lib/libdvm.so
02-22 14:47:40.070:信息/ DEBUG(28):beb3c85c beb3c918 [堆栈]
02-22 14:47:40.070:信息/ DEBUG(28):beb3c860 000024b8
02-22 14:47:40.090:信息/ DEBUG(28):beb3c864 fffacafc
02-22 14:47:40.090:信息/ DEBUG(28):beb3c868 00000000
02-22 14:47:40.100:信息/ DEBUG(28):beb3c86c 80faed2c
02-22 14:47:40.100:信息/ DEBUG(28):beb3c870 00000068
02-22 14:47:40.122:信息/ DEBUG(28):beb3c874 80dffdf3 /data/data/android.TestApp/lib/libDM.so
02-22 14:47:40.122:信息/ DEBUG(28):#01 beb3c878 80f510dc /data/data/android.TestApp/lib/libDM.so
02-22 14:47:40.122:信息/ DEBUG(28):beb3c87c 80faed2c
02-22 14:47:40.122:信息/ DEBUG(28):beb3c880 80fa45e0 /data/data/android.TestApp/lib/libDM.so
02-22 14:47:40.122:信息/ DEBUG(28):beb3c884 80f1cc31 /data/data/android.TestApp/lib/libDM.so
02-22 14:47:41.240:DEBUG /合子(30):由信号终止进程504(11)
您需要生成的地图的文件。在地图的文件包含在可执行文件中函数地址和内存位置。已经构建系统修改,以生成一个映射文件。
在地图的文件,可以使用文本编辑器和搜索地址。我曾经写了一个程序,找到两个符号边界一个给定的地址。对于像你这样的环境伟大的工作。
I am working on an Android program which calls in to native code. That native code is segfaulting, and since getting debugging working through the android NDK is not really doable, I'm left with a callstack like the following (captured from ddms). My question is whether there is something I can manually run after the fact to translate the memory addresses in the callstack to function names so I can see where this is segfaulting.
Thanks
02-22 14:47:39.231: DEBUG/dalvikvm(504): Trying to load lib /data/data/android.TestApp/lib/libDM.so 0x43b7c938
02-22 14:47:39.301: DEBUG/dalvikvm(504): Added shared lib /data/data/android.TestApp/lib/libDM.so 0x43b7c938
02-22 14:47:39.310: DEBUG/dalvikvm(504): No JNI_OnLoad found in /data/data/android.TestApp/lib/libDM.so 0x43b7c938
02-22 14:47:39.406: DEBUG/dalvikvm(504): +++ not scanning '/system/lib/libwebcore.so' for 'onLoadModel' (wrong CL)
02-22 14:47:39.410: DEBUG/dalvikvm(504): +++ not scanning '/system/lib/libmedia_jni.so' for 'onLoadModel' (wrong CL)
02-22 14:47:39.410: DEBUG/dalvikvm(504): +++ not scanning '/system/lib/libexif.so' for 'onLoadModel' (wrong CL)
02-22 14:47:39.410: DEBUG/dalvikvm(504): +++ not scanning '/system/lib/libsrec_jni.so' for 'onLoadModel' (wrong CL)
02-22 14:47:39.569: INFO/DEBUG(28): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-22 14:47:39.569: INFO/DEBUG(28): Build fingerprint: 'generic/sdk/generic/:2.1/ERD79/22607:eng/test-keys'
02-22 14:47:39.569: INFO/DEBUG(28): pid: 504, tid: 504 >>> android.TestApp <<<
02-22 14:47:39.569: INFO/DEBUG(28): signal 11 (SIGSEGV), fault addr 00000008
02-22 14:47:39.581: INFO/DEBUG(28): r0 00000000 r1 00000068 r2 00002350 r3 80facc00
02-22 14:47:39.581: INFO/DEBUG(28): r4 beb3c918 r5 000024b8 r6 fffacafc r7 0000aa98
02-22 14:47:39.581: INFO/DEBUG(28): r8 00000000 r9 000024b8 10 fffacafc fp 00000000
02-22 14:47:39.581: INFO/DEBUG(28): ip afbc30c8 sp beb3c858 lr 80dffdf3 pc 80dfb18a cpsr 40000030
02-22 14:47:39.711: INFO/DEBUG(28): #00 pc 001fb18a /data/data/android.TestApp/lib/libDM.so
02-22 14:47:39.733: INFO/DEBUG(28): #01 pc 001ffdee /data/data/android.TestApp/lib/libDM.so
02-22 14:47:39.740: INFO/DEBUG(28): #02 pc 0031cc2c /data/data/android.TestApp/lib/libDM.so
02-22 14:47:39.754: INFO/DEBUG(28): #03 pc 0031cd74 /data/data/android.TestApp/lib/libDM.so
02-22 14:47:39.761: INFO/DEBUG(28): #04 pc 0000f1f4 /system/lib/libdvm.so
02-22 14:47:39.769: INFO/DEBUG(28): #05 pc 00038018 /system/lib/libdvm.so
02-22 14:47:39.779: INFO/DEBUG(28): #06 pc 000316a2 /system/lib/libdvm.so
02-22 14:47:39.790: INFO/DEBUG(28): #07 pc 0003d31c /system/lib/libdvm.so
02-22 14:47:39.810: INFO/DEBUG(28): #08 pc 00013f58 /system/lib/libdvm.so
02-22 14:47:39.810: INFO/DEBUG(28): #09 pc 00019888 /system/lib/libdvm.so
02-22 14:47:39.820: INFO/DEBUG(28): #10 pc 00018d5c /system/lib/libdvm.so
02-22 14:47:39.846: INFO/DEBUG(28): #11 pc 0004d3bc /system/lib/libdvm.so
02-22 14:47:39.852: INFO/DEBUG(28): #12 pc 00054e74 /system/lib/libdvm.so
02-22 14:47:39.871: INFO/DEBUG(28): #13 pc 00013f58 /system/lib/libdvm.so
02-22 14:47:39.871: INFO/DEBUG(28): #14 pc 00019888 /system/lib/libdvm.so
02-22 14:47:39.889: INFO/DEBUG(28): #15 pc 00018d5c /system/lib/libdvm.so
02-22 14:47:39.889: INFO/DEBUG(28): #16 pc 0004d6d0 /system/lib/libdvm.so
02-22 14:47:39.900: INFO/DEBUG(28): #17 pc 0003a72c /system/lib/libdvm.so
02-22 14:47:39.909: INFO/DEBUG(28): #18 pc 0002be52 /system/lib/libdvm.so
02-22 14:47:39.921: INFO/DEBUG(28): #19 pc 00026cf4 /system/lib/libandroid_runtime.so
02-22 14:47:39.930: INFO/DEBUG(28): #20 pc 000279d8 /system/lib/libandroid_runtime.so
02-22 14:47:39.940: INFO/DEBUG(28): #21 pc 00008cae /system/bin/app_process
02-22 14:47:39.949: INFO/DEBUG(28): #22 pc 0000c2c6 /system/lib/libc.so
02-22 14:47:39.969: INFO/DEBUG(28): #23 pc b00018aa /system/bin/linker
02-22 14:47:39.981: INFO/DEBUG(28): code around pc:
02-22 14:47:39.981: INFO/DEBUG(28): 80dfb178 fffaaac8 4656b570 4644464d 4680b470
02-22 14:47:39.981: INFO/DEBUG(28): 80dfb188 6883b081 1c0d1c08 22b04798 46814442
02-22 14:47:39.981: INFO/DEBUG(28): 80dfb198 46921c10 f73d2600 4642ea90 6c546c13
02-22 14:47:39.981: INFO/DEBUG(28): code around lr:
02-22 14:47:39.981: INFO/DEBUG(28): 80dffde0 1c064a0b 589b447b 681c1c31 f7fb1c20
02-22 14:47:39.981: INFO/DEBUG(28): 80dffdf0 1c05f9c5 d0062800 d0042c00 23001c32
02-22 14:47:39.981: INFO/DEBUG(28): 80dffe00 f7fb1c20 1c28fa15 0000bd70 001a47f8
02-22 14:47:39.981: INFO/DEBUG(28): stack:
02-22 14:47:39.981: INFO/DEBUG(28): beb3c818 afe42ad4
02-22 14:47:39.981: INFO/DEBUG(28): beb3c81c ad07ff50 /system/lib/libdvm.so
02-22 14:47:39.990: INFO/DEBUG(28): beb3c820 0000bd00 [heap]
02-22 14:47:39.990: INFO/DEBUG(28): beb3c824 00000000
02-22 14:47:39.990: INFO/DEBUG(28): beb3c828 00085920 [heap]
02-22 14:47:40.000: INFO/DEBUG(28): beb3c82c 00000000
02-22 14:47:40.000: INFO/DEBUG(28): beb3c830 ffffffff
02-22 14:47:40.000: INFO/DEBUG(28): beb3c834 beb3c850 [stack]
02-22 14:47:40.015: INFO/DEBUG(28): beb3c838 00000000
02-22 14:47:40.015: INFO/DEBUG(28): beb3c83c 00000000
02-22 14:47:40.022: INFO/DEBUG(28): beb3c840 ad563b21 /system/lib/libicuuc.so
02-22 14:47:40.022: INFO/DEBUG(28): beb3c844 00085968 [heap]
02-22 14:47:40.030: INFO/DEBUG(28): beb3c848 00000001
02-22 14:47:40.050: INFO/DEBUG(28): beb3c84c 00000000
02-22 14:47:40.061: INFO/DEBUG(28): beb3c850 df002777
02-22 14:47:40.061: INFO/DEBUG(28): beb3c854 e3a070ad
02-22 14:47:40.070: INFO/DEBUG(28): #00 beb3c858 ad065714 /system/lib/libdvm.so
02-22 14:47:40.070: INFO/DEBUG(28): beb3c85c beb3c918 [stack]
02-22 14:47:40.070: INFO/DEBUG(28): beb3c860 000024b8
02-22 14:47:40.090: INFO/DEBUG(28): beb3c864 fffacafc
02-22 14:47:40.090: INFO/DEBUG(28): beb3c868 00000000
02-22 14:47:40.100: INFO/DEBUG(28): beb3c86c 80faed2c
02-22 14:47:40.100: INFO/DEBUG(28): beb3c870 00000068
02-22 14:47:40.122: INFO/DEBUG(28): beb3c874 80dffdf3 /data/data/android.TestApp/lib/libDM.so
02-22 14:47:40.122: INFO/DEBUG(28): #01 beb3c878 80f510dc /data/data/android.TestApp/lib/libDM.so
02-22 14:47:40.122: INFO/DEBUG(28): beb3c87c 80faed2c
02-22 14:47:40.122: INFO/DEBUG(28): beb3c880 80fa45e0 /data/data/android.TestApp/lib/libDM.so
02-22 14:47:40.122: INFO/DEBUG(28): beb3c884 80f1cc31 /data/data/android.TestApp/lib/libDM.so
02-22 14:47:41.240: DEBUG/Zygote(30): Process 504 terminated by signal (11)
You need to generate a map file. The map file contains the function address and memory locations in your executable. Have your build system modified to generate a map file.
From the map file, you can use a text editor and search for addresses. I once wrote a program to find the two symbols bounding a given address. Worked great for environments like yours.
这篇关于获得调用堆栈函数名的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!