uni-app中umeng上报的这种崩溃日志该如何处理呢?
uni-app中umeng上报的这种崩溃日志该如何处理呢?
Process Information
- Process Name: ‘xxx.xxx.xxx’
- Thread Name: ‘WeexJSBridgeThr’
- PID: 27239, TID: 27239 <<< com.plas.app <<<
- Forked from PID: 23137!
- Signal: 11 (SIGSEGV), Code 1 (SEGV_MAPERR), Fault addr bc1be664
Registers
r0 876db63f r1 ea06725c r2 136f4cd0 r3 0000000e
r4 0000000e r5 bc1be658 r6 eaf04600 r7 b80906c0
r8 b8090700 r9 cbeee400 10 cb6fe6e8 fp 13dbe2c8
ip 00000072 sp b80905c8 lr e5c6da5f pc e5c6d9a6 cpsr 40870030
d0 0000000000000000 d1 0000000000000000
d2 0000000000000000 d3 0000000000000000
d4 0000000000000000 d5 0000000000000000
d6 0000000000000000 d7 0000000000000000
d8 0000000000000000 d9 0000000000000000
d10 0000000000000000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 b8090a5000000000 d17 0000000000000000
d18 ffff000000000210 d19 0000ffff00004dee
d20 0000000000004de0 d21 0000ffff00004dee
d22 ffffffff00005fff d23 ac824800a9000000
d24 ae98ad88ad98aa38 d25 8ce8ade8adf8ae88
d26 ae98ad88ad98aa38 d27 8ce8ade8adf8ae88
d28 ac00ac00ac00a800 d29 8c00ac00ac00ac00
d30 0016000000000000 d31 8f8e8d8c8b8a8988
scr 20000010
Stack Trace
#00 pc 001a29a6 /apex/com.android.art/lib/libart.so (_ZN3art12ProfileSaver20ProcessProfilingInfoEbPtb)
#00 pc 001a29a6 /apex/com.android.art/lib/libart.so
#01 pc 001a2a5f /apex/com.android.art/lib/libart.so
--- --- ---
00 pc 001a29a6 /apex/com.android.art/lib/libart.so
01 pc 001a2a5b /apex/com.android.art/lib/libart.so
--- --- --- ---
Memory Dump
Memory near r0:
876db63c -------- -------- -------- -------- ................
Memory near r1:
ea06721c 00000000 00000000 00000000 00000000 ................
ea06722c 00000000 00000000 00000005 00000000 ................
ea06723c 00000000 00000000 00000000 00000000 ................
ea06724c 00000000 ffcdc370 00000000 00000000 ....p...........
ea06725c 876db63f 00000000 00000000 80000001 ?.m.............
Memory near r2:
136f4c90 70000000 00010001 0000000b 6fb0d380 ...p...........o
Memory near r5:
bc1be658 -------- -------- -------- -------- ................
Memory near r6:
eaf045c0 00000000 00000000 000000ff 00000000 ................
Memory near r7:
b8090680 00000000 00000000 00000000 00000000 ................
Memory near r8:
b80906c0 00001072 e5acbd00 00000000 00001017 r...............
Memory near r9:
cbeee3c0 0000001c ffffffff 10000008 00000001 ................
Memory near sl:
cb6fe6a8 00000000 e5ad9541 136f4cd0 10080009 ....A....Lo.....
Memory near fp:
13dbe288 136f4cd0 00000000 6fa2b9e0 00000008 .Lo........o....
Code Around PC
e5c6d964 f6bd4620 e788fdf5 f6bd4620 e78afdf1 F...... F......
Code Around LR
e5c6da1c d00207c0 f2819804 a805ec76 ec6af281 ........v.....j.
Stack
b8090588: 00000000 00000000 00000000 00000000
b8090598: 00000001 00000000 00000000 00000000
b80905a8: 12d4ba10 12d4ba10 00000000 00000000
b80905b8: 00000002 00000000 00000000 b80905b0
b80905c8: cbeee400 e5efdf78 ea06725c b8090700 #sp
更多关于uni-app中umeng上报的这种崩溃日志该如何处理呢?的实战教程也可以访问 https://www.itying.com/category-93-b0.html
2 回复
我自己这边测试没问题,主要是线上报的错,不知道怎么操作的,这个上传mapping文件有用吗?

