1 现象
当使用线刷刷入版本的时候,发现oobe第一次必定出现crash的情况。但是以后就再也不会出现crash的情况。
截取关键日志如下:
11-18 15:50:59.130 D/ActionGuard( 656): tag = MainActivity, on = false kkkkkk
11-18 15:50:59.160 F/libc ( 656): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 656 (tws.oobeprocess)
11-18 15:50:59.270 I/DEBUG ( 74): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-18 15:50:59.270 I/DEBUG ( 74): Build fingerprint: 'Ingenic/x3_iwop/watch:4.3/JLS36G/66:userdebug/test-keys'
11-18 15:50:59.270 I/DEBUG ( 74): Revision: '0'
11-18 15:50:59.270 I/DEBUG ( 74): pid: 656, tid: 656, name: tws.oobeprocess >>> com.tencent.tws.oobeprocess <<<
11-18 15:50:59.270 I/DEBUG ( 74): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
11-18 15:50:59.390 I/DEBUG ( 74): zr 00000000 at 00000001 v0 58390f70 v1 2b8134f0
11-18 15:50:59.390 I/DEBUG ( 74): a0 00000000 a1 7fa9cab0 a2 00000000 a3 583a85d8
11-18 15:50:59.390 I/DEBUG ( 74): t0 2c046ba0 t1 000005e4 t2 00000000 t3 00000000
11-18 15:50:59.390 I/DEBUG ( 74): t4 00000004 t5 ffffffff t6 00000003 t7 7fa9cab8
11-18 15:50:59.400 I/DEBUG ( 74): s0 55d043f0 s1 57feda98 s2 55d043f0 s3 00000001
11-18 15:50:59.400 I/DEBUG ( 74): s4 2cdee4a0 s5 2ce115c8 s6 7fa9cc68 s7 00000001
11-18 15:50:59.400 I/DEBUG ( 74): t8 00000001 t9 2cdc5038 k0 8af00025 k1 00000000
11-18 15:50:59.400 I/DEBUG ( 74): gp 2ce1a270 sp 7fa9ca68 s8 7fa9cb24 ra 2cdca954
11-18 15:50:59.400 I/DEBUG ( 74): hi 00000000 lo 00000030 bva 00000000 epc 2cdc507c
11-18 15:50:59.400 I/DEBUG ( 74):
11-18 15:50:59.400 I/DEBUG ( 74): backtrace:
11-18 15:50:59.400 I/DEBUG ( 74): #00 pc 0002d07c /system/lib/libhwui.so
11-18 15:50:59.400 I/DEBUG ( 74): #01 pc 0003294c /system/lib/libhwui.so
11-18 15:50:59.400 I/DEBUG ( 74): #02 pc 00032b18 /system/lib/libhwui.so
11-18 15:50:59.400 I/DEBUG ( 74): #03 pc 000925b8 /system/lib/libandroid_runtime.so
11-18 15:50:59.400 I/DEBUG ( 74): #04 pc 00022c24 /system/lib/libdvm.so (dvmPlatformInvoke+212)
11-18 15:50:59.400 I/DEBUG ( 74): #05 pc 00000001 <unknown>
从log来看,很有可能存在空指针的情况。