分析Unity崩溃日志(Android)-Toy模板网

这篇具有很好参考价值的文章主要介绍了分析Unity崩溃日志(Android)。希望对大家有所帮助。如果存在错误或未考虑完全的地方，请大家不吝赐教，您也可以点击"举报违法"按钮提交疑问。

Unity版本：

这里Unity版本是Unity 2019.4.30f1

崩溃信息：

错误信息如下：

Exception Appversion: versionName = 1.0.1 versionCode = 1
Process: sg.atla.f.c
PID: 22716
UID: 10749
Flags: 0x3088be44
Package: sg.atla.f.c v1 (1.0.1)
Foreground: Yes
Build: vivo/1938_2019/1938:10/QP1A.190711.020/compiler08241240:user/release-keys

java.lang.Error	*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Version '2019.4.30f1 (e8c891080a1f)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
Build fingerprint: 'vivo/1938_2019/1938:10/QP1A.190711.020/compiler08241240:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2024-01-12 21:47:31+0700
pid: 22716, tid: 24610, name: UnityMain  >>> sg.atla.f.c <<<
uid: 10749
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
Cause: null pointer dereference
    x0  0000000000000000  x1  0000007ec4fd4048  x2  0000000000000002  x3  0000000000000000
    x4  0000000000000000  x5  0000007e3362e9e4  x6  0000007dac9be800  x7  0000007dac9be800
    x8  0000007e336302b8  x9  0000000000000001  x10 0000000000000000  x11 0000000000000000
    x12 00000000000002d0  x13 0000000000000001  x14 0000000000000001  x15 0000007ca3c68c90
    x16 0000007dac6e9930  x17 0000007ec5255618  x18 0000007dc9c66000  x19 0000007dac76a000
    x20 0000007dac76a000  x21 00000000145fe518  x22 00000000144ff9a8  x23 0000000000000001
    x24 0000000012e80158  x25 0000000012e41d00  x26 0000000000000001  x27 0000000000000000
    x28 0000000000000000  x29 0000000000000001
    sp  0000007e3362ef80  lr  0000007dabaf0f78  pc  0000007dabaf0f78

backtrace:
      #00 pc 000000000032cf78  /data/app/sg.atla.f.c-X8gAZBdXGv-FRSH9Eo4oPg==/lib/arm64/libunity.so (BuildId: a4ee0b5e1f43348c0be087ab5049fdb15ed93758)
      #01 pc 000000000032e1a4  /data/app/sg.atla.f.c-X8gAZBdXGv-FRSH9Eo4oPg==/lib/arm64/libunity.so (BuildId: a4ee0b5e1f43348c0be087ab5049fdb15ed93758)
      #02 pc 000000000032fe70  /data/app/sg.atla.f.c-X8gAZBdXGv-FRSH9Eo4oPg==/lib/arm64/libunity.so (BuildId: a4ee0b5e1f43348c0be087ab5049fdb15ed93758)
      #03 pc 0000000000092694  /data/app/sg.atla.f.c-X8gAZBdXGv-FRSH9Eo4oPg==/oat/arm64/base.odex

-2
java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version     : 2019.4.30f1
Device model      : vivo vivo 2019
Device fingerprint: vivo/1938_2019/1938:10/QP1A.190711.020/compiler08241240:user/release-keys

Caused by: java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Version '2019.4.30f1 (e8c891080a1f)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
Build fingerprint: 'vivo/1938_2019/1938:10/QP1A.190711.020/compiler08241240:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2024-01-12 21:47:31+0700
pid: 22716, tid: 24610, name: UnityMain  >>> sg.atla.f.c <<<
uid: 10749
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
Cause: null pointer dereference
    x0  0000000000000000  x1  0000007ec4fd4048  x2  0000000000000002  x3  0000000000000000
    x4  0000000000000000  x5  0000007e3362e9e4  x6  0000007dac9be800  x7  0000007dac9be800
    x8  0000007e336302b8  x9  0000000000000001  x10 0000000000000000  x11 0000000000000000
    x12 00000000000002d0  x13 0000000000000001  x14 0000000000000001  x15 0000007ca3c68c90
    x16 0000007dac6e9930  x17 0000007ec5255618  x18 0000007dc9c66000  x19 0000007dac76a000
    x20 0000007dac76a000  x21 00000000145fe518  x22 00000000144ff9a8  x23 0000000000000001
    x24 0000000012e80158  x25 0000000012e41d00  x26 0000000000000001  x27 0000000000000000
    x28 0000000000000000  x29 0000000000000001
    sp  0000007e3362ef80  lr  0000007dabaf0f78  pc  0000007dabaf0f78

backtrace:
      #00 pc 000000000032cf78  /data/app/sg.atla.f.c-X8gAZBdXGv-FRSH9Eo4oPg==/lib/arm64/libunity.so (BuildId: a4ee0b5e1f43348c0be087ab5049fdb15ed93758)
      #01 pc 000000000032e1a4  /data/app/sg.atla.f.c-X8gAZBdXGv-FRSH9Eo4oPg==/lib/arm64/libunity.so (BuildId: a4ee0b5e1f43348c0be087ab5049fdb15ed93758)
      #02 pc 000000000032fe70  /data/app/sg.atla.f.c-X8gAZBdXGv-FRSH9Eo4oPg==/lib/arm64/libunity.so (BuildId: a4ee0b5e1f43348c0be087ab5049fdb15ed93758)
      #03 pc 0000000000092694  /data/app/sg.atla.f.c-X8gAZBdXGv-FRSH9Eo4oPg==/oat/arm64/base.odex
  at libunity
  at libunity
  at libunity
  at base

关键信息解释：

注意关键信息’arm64-v8a’ ABI: ‘arm64’ 这里是指arm64的崩溃，需要找arm64-v8a的符号表，其它符号表按照次逻辑查找。
libil2cpp指libil2cpp.sym.so文件
libunity指libunity.sym.so文件

so文件位置：

{项目编译后路径}\Temp\StagingArea\symbols

2、导出安卓工程的时候，选择Create symbols.zip，此时符号表压缩包会在导出安卓工程目录下面

符号化工具位置：

E:\software\unity\2019.4.30f1\Editor\Data\PlaybackEngines\AndroidPlayer\NDK\toolchains\llvm\prebuilt\windows-x86_64\bin

分析Unity崩溃日志(Android),Unity,unity,android,游戏引擎,崩溃日志定位
aarch64-linux-android-addr2line 这个是arm64的
arm-linux-androideabi-addr2line 这个是arm32的

cd到addr2line目录

.\aarch64-linux-android-addr2line.exe -f -C -e C:\Users\jisufeichi\Desktop\symbols\arm64-v8a\libunity.sym.so 0x032cf78 0x032e1a4 0x032fe70 0x0092694

解析结果：

分析Unity崩溃日志(Android),Unity,unity,android,游戏引擎,崩溃日志定位文章来源地址https://www.toymoban.com/news/detail-809491.html

到了这里，关于分析Unity崩溃日志(Android)的文章就介绍完了。如果您还想了解更多内容，请在右上角搜索TOY模板网以前的文章或继续浏览下面的相关文章，希望大家以后多多支持TOY模板网！

分析Unity崩溃日志(Android)

Unity版本：

崩溃信息：

关键信息解释：

so文件位置：

符号化工具位置：

解析结果：

觉得文章有用就打赏一下文章作者

支付宝扫一扫打赏

微信扫一扫打赏

支付宝扫一扫领取红包，优惠每天领

二维码1

二维码2