crash analysis

It is always inevitable to encounter some crash problems. Mastering some common commands can quickly locate the problem and avoid repeated copying problems.

1. First we will get the stack info and backtrace of the crash.

09-14 09:38:22.018   364  1748 D audiohal_stream_offload: qz = 0 readAddr = 0xf23d8906 writeSize = 2246 sizeRemain = 30522
--------- beginning of crash
09-14 09:38:22.018   364  1748 F libc    : Fatal signal 7 (SIGBUS), code 1 (BUS_ADRALN), fault addr 0xf23d8912 in tid 1748 (writer), pid 364 (audio.service)
01-01 00:03:57.532  1749  1749 W AUD[0] thread: start
01-01 00:03:57.544   316   316 E         : {MENU}DEC2 Codec=3
09-14 09:38:22.058  1752  1752 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstoneProto
09-14 09:38:22.059   262   262 I tombstoned: received crash request for pid 1748
09-14 09:38:22.059  1752  1752 I crash_dump32: performing dump of process 364 (target tid = 1748)
09-14 09:38:22.064  1752  1752 E DEBUG   : failed to read /proc/uptime: Permission denied
01-01 00:03:57.561     0     0 F  

Guess you like

Origin blog.csdn.net/dreamDay2016_11_11/article/details/127086386