Search Unity

Symbolicate IL2CPP crash

Discussion in 'Android' started by clevergamesdev, Aug 14, 2019.

  1. clevergamesdev

    clevergamesdev

    Joined:
    Jun 20, 2019
    Posts:
    17
    Hi,

    I have the following native crash log (below):

    java.lang.Error: FATAL EXCEPTION [UnityMain]
    Unity version : 2018.4.6f1
    Device model : samsung SM-G965F
    Device fingerprint: samsung/star2ltexx/star2lte:9/PPR1.180610.011/G965FXXU6CSG8:user/release-keys

    Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000000000000040 Build fingerprint: 'samsung/star2ltexx/star2lte:9/PPR1.180610.011/G965FXXU6CSG8:user/release-keys' Revision: '26'
    pid: 21634, tid: 21773, name: UnityMain >>> com.game.basketball <<<
    x0 0000000000000040 x1 0000000000000001 x2 0000006f23800000 x3 000000000000000c x4 00000000000000b2 x5 0000006f4243ad48 x6 0000006f1940d640 x7 0000006f191dfec0 x8 0000000000000000 x9 0000000000000001 x10 0000000000000000 x11 0000000000000000 x12 0000000000000003 x13 0000000000000000 x14 0000000000000002 x15 0000000000000001 x16 0000006fcdeb0bd8 x17 0000006fcde46658 x18 0000000000000001 x19 0000006f2284b3c0 x20 0000000000000000 x21 0000000000000000 x22 0000006f325c5dd0 x23 0000006f32e17c72 x24 0000000000000004 x25 0000006f325c7588 x26 0000006f3029a4a0 x27 0000006f228566c0 x28 0000000000000002 x29 0000006f325c5bf8 x30 0000006f2c0d9374 sp 0000006f325c5940 pc 0000006f2be983c0 pstate 0000000060000000

    at [vdso].(

    at split_config.__null__ (split_config.java)

    at split_config.__null__ (split_config.java)

    at split_config.__null__ (split_config.java)

    at split_config.__null__ (split_config.java)

    at split_config.__null__ (split_config.java)

    at split_config.__null__ (split_config.java)

    at split_config.__null__ (split_config.java)

    at split_config.__null__ (split_config.java)

    at split_config.__null__ (split_config.java)

    at split_config.__null__ (split_config.java)

    at base.__null__ (base.java)


    Looking at Unity Symbolicate Tutorial, it seems that the structure of the crash log that they have there, is different then what I see in Play Console crash logs.
    How can I Symbolicate the following log for instance?

    Thanks.
     
    Last edited: Aug 16, 2019
    clevergamesdev, Aug 14, 2019
    #1

  2. clevergamesdev

    clevergamesdev

    Joined:
    Jun 20, 2019
    Posts:
    17
    Hi, can someone try to help?
     
    clevergamesdev, Aug 16, 2019
    #2

  3. shishaoguang1

    shishaoguang1

    Joined:
    Jul 15, 2021
    Posts:
    3
    i have the same problem could not find solution
     
    shishaoguang1, Aug 18, 2021
    #3

  4. kaarloew

    kaarloew

    Joined:
    Nov 1, 2018
    Posts:
    360
    kaarloew, Aug 18, 2021
    #4

  5. shishaoguang1

    shishaoguang1

    Joined:
    Jul 15, 2021
    Posts:
    3
    but i can't watch stacktrace in crash log .
    It's just show "split_config.__null__" .i don't know why?
    I'm using AppBundle to upload Google Play.
    there are many of them, some one help me please

    this is log :
    java.lang.Error

    java.lang.Error: FATAL EXCEPTION [UnityMain]
    Unity version : 2019.2.18f1
    Device model : samsung SM-G973U
    Device fingerprint: samsung/beyond1qltesq/beyond1q:11/RP1A.200720.012/G973USQS5GUF1:user/release-keys

    Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000007c4b2f8ec0
    Build fingerprint: 'samsung/beyond1qltesq/beyond1q:11/RP1A.200720.012/G973USQS5GUF1:user/release-keys'
    Revision: '17'
    pid: 5872, tid: 8447, name: UnityMain >>> com.xxxx.xxxx <<<
    x0 0000007c4b2f8ec0 x1 0000000000000000 x2 00000000000006a8 x3 0000007c4b2f8ec0
    x4 0000007c4b2f9568 x5 0000000000000004 x6 0000007c4b972900 x7 0000007c5408d600
    x8 0000007c4b2f9c70 x9 0000007bc30f5000 x10 0000000000010ab4 x11 0000000000000000
    x12 000000000000000d x13 000000000001dfe0 x14 0000000000000ea0 x15 0000000000000000
    x16 0000007bc2de3c30 x17 0000007f5b715d40 x18 0000000000000036 x19 0000007b82051fe0
    x20 0000007c4b2f9a50 x21 0000007c4b2f8ec0 x22 0000000000000000 x23 0000007c54ab5000
    x24 0000000000000000 x25 0000000000000280 x26 0000000000000018 x27 aaaaaaaaaaaaaaab
    x28 000000000000003f x29 0000007c4b2f9590 x30 0000007bbf843d68
    sp 0000007c4b2f8ec0 pc 0000007f5b715dcc pstate 0000000020000000

    at [vdso].(
    at libc.memset (memset:136)
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
    at split_config.__null__
     
    shishaoguang1, Aug 31, 2021
    #5

  6. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    3,900
    You're using 2019.2.18f1, which is no longer supported, please switch to 2019 LTS and see if it still reproduces for you
     
    Tomas1856, Aug 31, 2021
    #6

  7. shishaoguang1

    shishaoguang1

    Joined:
    Jul 15, 2021
    Posts:
    3
    ok i will try thanks.
    Is there fixed in LTS?
     
    shishaoguang1, Sep 1, 2021
    #7

  8. kaarloew

    kaarloew

    Joined:
    Nov 1, 2018
    Posts:
    360
    Hard to say since we do not know if your symbolication went correctly, and so we do not know what is the cause of the crash.
     
    kaarloew, Sep 2, 2021
    #8