android_system_core/debuggerd/libdebuggerd
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
..
include/libdebuggerd debuggerd: use One True timestamp function. 2020-07-23 16:33:53 -07:00
test debuggerd: use One True timestamp function. 2020-07-23 16:33:53 -07:00
backtrace.cpp debuggerd: use One True timestamp function. 2020-07-23 16:33:53 -07:00
gwp_asan.cpp Move PC-only unwind frame generation to libunwindstack. 2020-03-26 13:39:05 -07:00
open_files_list.cpp libdebuggerd: decode fdsan owner tags. 2018-08-28 13:48:08 -07:00
scudo.cpp Add support for MTE error reports in tombstones. 2020-04-27 13:15:49 -07:00
tombstone.cpp debuggerd: use One True timestamp function. 2020-07-23 16:33:53 -07:00
utility.cpp debuggerd: use One True timestamp function. 2020-07-23 16:33:53 -07:00