Hello folks,
I'm trying to use MGD for tracing on an unrooted Oppo F1s device but everytime I run my app with "Enable MGD Daemon" enabled, the app will crash.
Below is the logged stack trace (I'm using unrooted Arm v7 libMGD.so) :
12-05 13:49:28.772: I/AEE/AED(22348): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 12-05 13:49:28.772: I/AEE/AED(22348): Build fingerprint: 'OPPO/A1601/A1601:6.0/MRA58K/1487939108:user/release-keys' 12-05 13:49:28.772: I/AEE/AED(22348): Revision: '0' 12-05 13:49:28.772: I/AEE/AED(22348): ABI: 'arm' 12-05 13:49:28.772: I/AEE/AED(22348): pid: 22236, tid: 22271, name: GLThread 279 >>> somegame <<< 12-05 13:49:28.773: I/AEE/AED(22348): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x38 12-05 13:49:28.786: E/WindowManager(1098): Unknown window type: 2301 12-05 13:49:28.787: I/SurfaceFlinger(326): [Built-in Screen (type:0)] fps:60.028336,dur:1016.19,max:23.57,min:12.38 12-05 13:49:28.794: I/AEE/AED(22348): r0 e1de8c0c r1 00000034 r2 d44b5200 r3 d44b5224 12-05 13:49:28.794: I/AEE/AED(22348): r4 d44b521c r5 00000000 r6 d4e441f9 r7 d44b520c 12-05 13:49:28.794: I/AEE/AED(22348): r8 e1de90c0 r9 e7c508e9 sl e1dea5b8 fp 00000000 12-05 13:49:28.794: I/AEE/AED(22348): ip ee84e1e0 sp d44b51e0 lr d49d3a79 pc d49d0714 cpsr a00f0030 12-05 13:49:28.796: I/AEE/AED(22348): backtrace: 12-05 13:49:28.797: I/AEE/AED(22348): #00 pc 001da714 /data/app/somegame/lib/arm/libMGD.so 12-05 13:49:28.797: I/AEE/AED(22348): #01 pc 001dda75 /data/app/somegame/lib/arm/libMGD.so 12-05 13:49:28.797: I/AEE/AED(22348): #02 pc 0019557d /data/app/somegame/lib/arm/libMGD.so 12-05 13:49:28.797: I/AEE/AED(22348): #03 pc 000ad963 /data/app/somegame/lib/arm/libMGD.so (eglSwapBuffers+62) 12-05 13:49:28.797: I/AEE/AED(22348): #04 pc 00066d47 /system/lib/libandroid_runtime.so 12-05 13:49:28.797: I/AEE/AED(22348): #05 pc 0305ebf9 /system/framework/arm/boot.oat (offset 0x2625000)
My MGD version is 4.8.0.b82d70a1.
GPU is Mali-T860, Android version is 6.0.
Any help is appreciated .Thank you.
Hello,
Thanks for bringing this to our attention. I took a look at this stack trace this morning. I don't think there's enough information in the stack trace to identify the issue. Could you provide us with the entire logcat output when you experience the crash?