platform_system_core/debuggerd/libdebuggerd
Josh Gao bf2dd48241 crash_dump: during early boot, output to kmsg on userdebug.
Crashes that happen before tombstoned is running are extremely hard to
diagnose, because tombstones aren't written to disk, and the window of
opportunity to get logs via `adb logcat` is small (potentially
nonexistent).

Solve this by adding a world-writable /dev/kmsg_debug on userdebug
builds, and writing to it in addition to logcat when tombstoned hasn't
started yet.

Bug: http://b/36574794
Test: stop tombstoned; crasher; dmesg
Change-Id: Ib22c02a002afb602933155fb2c9b7a8abbe9ed38
2017-04-06 15:00:52 -07:00
..
arm debuggerd: advance our amazing bet. 2017-01-17 13:57:57 -08:00
arm64 debuggerd: advance our amazing bet. 2017-01-17 13:57:57 -08:00
include crash_dump: fetch process/thread names before dropping privileges. 2017-03-15 23:30:14 -07:00
mips debuggerd: advance our amazing bet. 2017-01-17 13:57:57 -08:00
mips64 debuggerd: advance our amazing bet. 2017-01-17 13:57:57 -08:00
test Initialize si_code in siginfo. 2017-03-22 18:06:57 -07:00
x86 debuggerd: advance our amazing bet. 2017-01-17 13:57:57 -08:00
x86_64 debuggerd: advance our amazing bet. 2017-01-17 13:57:57 -08:00
backtrace.cpp crash_dump: fetch process/thread names before dropping privileges. 2017-03-15 23:30:14 -07:00
elf_utils.cpp debuggerd: advance our amazing bet. 2017-01-17 13:57:57 -08:00
open_files_list.cpp debuggerd: advance our amazing bet. 2017-01-17 13:57:57 -08:00
tombstone.cpp Do not access device maps. 2017-03-22 14:55:05 -07:00
utility.cpp crash_dump: during early boot, output to kmsg on userdebug. 2017-04-06 15:00:52 -07:00