Android NDK开发Crash错误定位:


D:\Users\Android\Sdk
ndk-stack.exe:
D:\Users\Android\Sdk\ndk-bundle\prebuilt\windows-x86_64\bin
aarch64-linux-android-addr2line.exe:
D:\Users\Android\Sdk\ndk-bundle\toolchains\
aarch64-linux-android-4.9\prebuilt\windows-x86_64\bin
aarch64-linux-android-objdump.exe:
D:\Users\Android\Sdk\ndk-bundle\toolchains\
aarch64-linux-android-4.9\prebuilt\windows-x86_64\bin

可以查看手机的CPU信息:
adb shell cat /proc/cpuinfo

AArch64表示Arm64位
(1)
方式1:使用arm-linux-androideabi-addr2line 定位出错位置


aarch64-linux-android-addr2line.exe:
D:\Users\Android\Sdk\ndk-bundle\toolchains\aarch64-linux-android-4.9\prebuilt\windows-x86_64\bin
出错的汇编指令地址:

00004136
000041f7
-e:指定so文件路径

注意:
stripDebugSymbol里的lib无法addr2line
mergeJniLibs里的lib可以addr2line

(2)方式2:使用arm-linux-androideabi-objdump 定位出错的函数信息
下面我们来看一下怎么来定位函数的信息:
00004136
000041f7



(3)方式3:ndk-stack
adb logcat的log通过ndk-stack可以看到crash的具体接口的行数,前提是
非strip的lib库

