diff options
| author | Elliott Hughes <enh@google.com> | 2020-07-23 15:26:10 -0700 |
|---|---|---|
| committer | Elliott Hughes <enh@google.com> | 2020-07-23 16:33:53 -0700 |
| commit | a660cb3f13ad369554678ea19753cbc7e92726f3 (patch) | |
| tree | 3559b09f77391adc9c74016ff9d9d2e52d2d1fb2 /libutils/Unicode.cpp | |
| parent | 4aa073337d6b872ff87b702c4dcfa26142e6c9c2 (diff) | |
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
Diffstat (limited to 'libutils/Unicode.cpp')
0 files changed, 0 insertions, 0 deletions