a660cb3f13
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 |
||
|---|---|---|
| .. | ||
| backtrace.h | ||
| gwp_asan.h | ||
| open_files_list.h | ||
| scudo.h | ||
| tombstone.h | ||
| types.h | ||
| utility.h | ||