【log理解】是由于缺少read权限导致的crash吗？

2020-02-25 11:20:07 1.6k 阅读 AI 写同款 · GEO 优化AI 选题数据监测一键分发 ›

redo log和bin log以及两阶段提交（笔记） 1.redo log 如果熟悉MySQL你肯定知道MySQL能过对数据进行恢复（前提是开启bin log日志），当然这要归功于bin log日志。但是你可曾听过redo log呢？首先redo log是innodb引擎特有的，需要注意的是innodb是MySQL的一个插件。什么是redo log呢？有啥用？实际上当我们执行一条修改语句，难道每次都要落盘吗？显然是不可能的，如果每次都需要落盘，首先数据量大的时候每次都要去对这么大的文件进行io操作，显然在效率上是不可行的。那么redo lo 阅读详情

gts测试log，如下红色部分，是由于前面的 fault addr 导致的crash，那fault addr是由于缺少 read 权限导致的吗？
还是与这个权限无关呢？
02-24 09:00:43.198 818 16229 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x35e in tid 16229 (HwBinder:818_3), pid 818 (drm@1.2-service)

02-24 09:00:43.195 818 818 W HwBinder:818_3: type=1400 audit(0.0:21338): avc: denied { read } for name="u:object_r:persist_debug_prop:s0" dev="tmpfs" ino=16940 scontext=u:r:hal_drm_widevine:s0 tcontext=u:object_r:persist_debug_prop:s0 tclass=file permissive=0

完整log：

02-24 09:00:43.151   818 16229 I WVCdm   : [cdm_engine.cpp(326):AddKey] CdmEngine::AddKey: sid178

02-24 09:00:43.151   818 16229 I WVCdm   : [usage_table_header.cpp(144):AddEntry] UsageTableHeader::AddEntry: Lock

02-24 09:00:43.151   818 16229 I WVCdm   : [usage_table_header.cpp(195):AddEntry] UsageTableHeader::AddEntry: usage entry #: 58

02-24 09:00:43.198   818 16229 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x35e in tid 16229 (HwBinder:818_3), pid 818 (drm@1.2-service)

02-24 09:00:43.198   818 16229 E libc    : Access denied finding property "persist.debug.coredump"

02-24 09:00:43.195   818   818 W HwBinder:818_3: type=1400 audit(0.0:21338): avc: denied { read } for name="u:object_r:persist_debug_prop:s0" dev="tmpfs" ino=16940 scontext=u:r:hal_drm_widevine:s0 tcontext=u:object_r:persist_debug_prop:s0 tclass=file permissive=0

02-24 09:00:43.214   812  1561 E CHIUSECASE: [ERROR  ] chxextensionmodule.cpp:613 MonitorThreadProcessing() open /proc/self/statm ret 0 mCameraOpen 1 buffer 808984 30557 15166 3 0 151612 0

02-24 09:00:43.214   812  1561 E CHIUSECASE:  

02-24 09:00:43.237 16440 16440 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone

02-24 09:00:43.240  1262  1262 I /system/bin/tombstoned: received crash request for pid 16229

02-24 09:00:43.241 16440 16440 I crash_dump64: performing dump of process 818 (target tid = 16229)

02-24 09:00:43.242 16440 16440 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

02-24 09:00:43.243 16440 16440 F DEBUG   : Build fingerprint: 'meizu/m2081/m2081:10/QKQ1.200127.002/1582477560:user/release-keys'

02-24 09:00:43.243 16440 16440 F DEBUG   : Revision: '0'

02-24 09:00:43.243 16440 16440 F DEBUG   : ABI: 'arm64'

02-24 09:00:43.243 16440 16440 F DEBUG   : Timestamp: 2020-02-24 09:00:43+0000

02-24 09:00:43.243 16440 16440 F DEBUG   : pid: 818, tid: 16229, name: HwBinder:818_3  >>> /vendor/bin/hw/android.hardware.drm@1.2-service.widevine <<<

02-24 09:00:43.243 16440 16440 F DEBUG   : uid: 1013

02-24 09:00:43.243 16440 16440 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x35e

02-24 09:00:43.243 16440 16440 F DEBUG   : Cause: null pointer dereference

02-24 09:00:43.243 16440 16440 F DEBUG   :     x0  0000000000000000  x1  000000000000006b  x2  00000000000000dc  x3  000000003c6ef35f

02-24 09:00:43.243 16440 16440 F DEBUG   :     x4  000000000000660d  x5  000000000019660d  x6  000000000000000b  x7  000000000000c146

02-24 09:00:43.243 16440 16440 F DEBUG   :     x8  00000076d0c5b440  x9  0000000000000001  x10 0000000000000001  x11 00000076ce805750

02-24 09:00:43.243 16440 16440 F DEBUG   :     x12 0000000000000000  x13 0000000000000001  x14 00000076ce805780  x15 000000000000009b

02-24 09:00:43.243 16440 16440 F DEBUG   :     x16 00000076d0c427a8  x17 00000076d06c7280  x18 0000000000000069  x19 0000000000000353

02-24 09:00:43.243 16440 16440 F DEBUG   :     x20 00000000c23f5008  x21 00000076d0bfd52f  x22 000000000000044c  x23 00000076d18b0000

02-24 09:00:43.243 16440 16440 F DEBUG   :     x24 00000076d0c5b5b8  x25 00000076d0bee0cf  x26 00000076cc5ffb80  x27 000000005ff3a98d

02-24 09:00:43.243 16440 16440 F DEBUG   :     x28 0009850bc021bd88  x29 00000076cc5ffaf0

02-24 09:00:43.243 16440 16440 F DEBUG   :     sp  00000076cc5ffaf0  lr  00000076d18ae16c  pc  00000076d18ae1cc

02-24 09:00:43.308 16440 16440 F DEBUG   : 

02-24 09:00:43.308 16440 16440 F DEBUG   : backtrace:

02-24 09:00:43.308 16440 16440 F DEBUG   :       #00 pc 00000000000001cc  <anonymous:76d18ae000>

02-24 09:00:43.357  1607  2544 W NativeCrashListener: Couldn't find ProcessRecord for pid 818

02-24 09:00:43.358 16440 16440 E crash_dump64: AM data write failed: Broken pipe

02-24 09:00:43.360  1262  1262 E /system/bin/tombstoned: Tombstone written to: /data/tombstones/tombstone_00