Android App crash attaching a debugger, signal 11

Unity Engine
,
1

Hi there,
I’m trying to debug (with breakpoints) an Android app.
As soon as I attach the debugger (C# Rider in this case but I got same behaviour with Mono) to the android player, the app stuck then crash with this funny message:

04-06 14:25:50.586: E/AndroidRuntime(1802): FATAL EXCEPTION: UnityMain
04-06 14:25:50.586: E/AndroidRuntime(1802): Process: com.mycompany.test, PID: 1802
04-06 14:25:50.586: E/AndroidRuntime(1802): java.lang.Error: FATAL EXCEPTION [UnityMain]
04-06 14:25:50.586: E/AndroidRuntime(1802): Unity version     : 2017.3.1f1
04-06 14:25:50.586: E/AndroidRuntime(1802): Device model      : HUAWEI BLN-L21
04-06 14:25:50.586: E/AndroidRuntime(1802): Device fingerprint: HONOR/BLN-L21/HWBLN-H:7.0/HONORBLN-L21/C432B371:user/release-keys
04-06 14:25:50.586: E/AndroidRuntime(1802): Caused by: java.lang.Error: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr e716b000
04-06 14:25:50.586: E/AndroidRuntime(1802): Build fingerprint: 'HONOR/BLN-L21/HWBLN-H:7.0/HONORBLN-L21/C432B371:user/release-keys'
04-06 14:25:50.586: E/AndroidRuntime(1802): Revision: '0'
04-06 14:25:50.586: E/AndroidRuntime(1802): pid: 1802, tid: 1821, name: UnityMain  >>> com.mycompany.test <<<
04-06 14:25:50.586: E/AndroidRuntime(1802):     r0 00000000  r1 e13f2d88  r2 e13f2e14  r3 c77237f8
04-06 14:25:50.586: E/AndroidRuntime(1802):     r4 c5759c10  r5 e13f2e14  r6 00000000  r7 00000000
04-06 14:25:50.586: E/AndroidRuntime(1802):     r8 00000000  r9 db540700  sl 12c16fc0  fp e13f2b30
04-06 14:25:50.586: E/AndroidRuntime(1802):     ip e13f2b70  sp e13f2b30  lr e716b000  pc c7723ba4  cpsr e718bd10
04-06 14:25:50.586: E/AndroidRuntime(1802):     at Unknown.00003ba4(Unknown Source)
04-06 14:25:50.586: E/AndroidRuntime(1802):     at Unknown.00000ffc(Unknown Source)

Any Idea of what it could be?

2

Same here. Please some help?

Tried with IP and USB way. No luck.

1 Like
3

A similar issue was reported in https://answers.unity.com/answers/1803074/view.html. For me, switching Scripting Backend from IL2CPP to Mono solved the problem.