Help to analyze stack traces

Unity Engine
, ,
1

I did find generic guides to help me analyzing stack traces but, since a few months, I’m plagued by java.lang.error happening in my application only with android 8.1 and 9.0 that I’m not able to understand.
I get the stack traces from Google Play but I really cannot figure out they happen.

I used aarch64-linux-android-addr2line.exe" -f -C -e libil2cpp.sym.so but I get method names that don’t tell me anything.

For example, for the crash below I see something like this:

libil2cpp.0x52f3b0 (il2cpp::vm::Method::GetParamCount(MethodInfo const*))
libunity.0x2e4c68 (scripting_method_invoke(ScriptingMethodPtr, ScriptingObjectPtr, ScriptingArguments&, ScriptingExceptionPtr*, bool))
libunity.0x2f10f8 (ScriptingInvocation::Invoke(ScriptingExceptionPtr*, bool))
libunity.0x167770 (UnityJavaProxy_invoke(_JNIEnv*, _jobject*, long, _jstring*, _jobjectArray*))

How would a Unity expert proceed to analyze the problem?

java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Version ‘2019.4.1f1 (e6c045e14e4e)’, Build type ‘Release’, Scripting Backend ‘il2cpp’, CPU ‘arm64-v8a’
Build fingerprint: ‘HUAWEI/ANE-LX2/HWANE:9/HUAWEIANE-L22/9.1.0.287C636:user/release-keys’
Revision: ‘0’
ABI: ‘arm64’
Timestamp: 2020-07-20 17:42:09+0700
pid: 25200, tid: 25657, name: Thread-100 >>> net.homeip.alphabet <<<
uid: 10018
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4a
Cause: null pointer dereference
x0 0000000000000000 x1 0000000000000000 x2 000000765bc65670 x3 000000765bc657a0
x4 0000000000000000 x5 0000000000000005 x6 000000765b3d7df0 x7 000000765b3ec610
x8 000000765940e124 x9 000000000000000a x10 0000000000004001 x11 0000000000000000
x12 000000765a631000 x13 0000000000000001 x14 0000000000000236 x15 0000007651208f08
x16 000000765d6301e0 x17 00000077020202b0 x18 000000765a639000 x19 000000765bc657a0
x20 0000000000000000 x21 0000000000000000 x22 000000765bc65670 x23 0000000000000003
x24 0000000000000000 x25 000000765bc67588 x26 00000076726508a0 x27 0000000000000004
x28 0000000000000000 x29 000000765bc658c8
sp 000000765bc655e0 lr 000000765c98cc6c pc 00000076594403b0
backtrace:
at .
at .
at .
at .
at .
at libil2cpp.0x52f3b0 (Native Method)
at libunity.0x2e4c68 (Native Method)
at libunity.0x2f10f8 (Native Method)
at libunity.0x167770 (Native Method)
at base.0x8cb40 (Native Method)

2

I am kicking this up.

If I do e.g.
./aarch64-linux-android-addr2line -f -C -e somepath/arm64-v8a/libil2cpp.so 415b50

./aarch64-linux-android-addr2line -f -C -e somepath/arm64-v8a/libil2cpp.so 0x415b50

./aarch64-linux-android-addr2line -f -C -e somepath/arm64-v8a/libil2cpp.so 0000000000415b50

I only get ? as result. The 415b50 is from stack trace and ibil2cpp.so is the libil2cpp.sym file that is generated during the build process.

So how should I do this?

3

Try reading this - Stacktrace Utility | Android Logcat | 1.2.3 it might help you figure out where to find symbol files.

4

Thanks. I tried, and still no results. Resolved text is exactly same as original (well text is bold + italic, but content is same).

5

Manually following works