Elliott Hughes a660cb3f13 debuggerd: use One True timestamp function. ... An OEM asks for sub-second granularity, and that's most easily done if we only have one timestamp generator. I'm not convinced sub-second granularity is particularly useful myself, and I definitely don't think that nanosecond resolution is meaningful but I do like this cleanup, and if I'm going to use sub-second precision I may as well use the maximum precision available to me. Also reduce some duplication of code reading cmdline/comm. Bug: https://issuetracker.google.com/161860597 Test: head /data/tombstones/* Change-Id: I035ecfd4a3338ccd84dae0ef973a998a7c7c5056		2020-07-23 16:33:53 -07:00
..
sys	There's no longer a limit to property names.	2017-02-28 14:12:54 -08:00
dump_memory_test.cpp	Include the map name when dumping memory around a register.	2018-02-15 16:28:50 -08:00
elf_fake.cpp	crash_dump: fork a copy of the target's address space.	2017-12-15 14:11:12 -08:00
elf_fake.h	debuggerd: advance our amazing bet.	2017-01-17 13:57:57 -08:00
host_signal_fixup.h	debuggerd: advance our amazing bet.	2017-01-17 13:57:57 -08:00
log_fake.cpp	libdebuggerd: cleanup.	2017-08-29 15:18:46 -07:00
log_fake.h	debuggerd: advance our amazing bet.	2017-01-17 13:57:57 -08:00
open_files_list_test.cpp	switch to using android-base/file.h instead of android-base/test_utils.h	2018-11-14 09:35:34 -08:00
tombstone_test.cpp	debuggerd: use One True timestamp function.	2020-07-23 16:33:53 -07:00
UnwinderMock.h	Replace libbacktrace with libunwindstack directly.	2019-01-29 17:57:14 -08:00