Ted Unangst wrote:
> Philip Guenther wrote:
> > I think it would be better to include the clock_t value in the
> > timespec struct tracing, then branch on that.
>
> I of course looked at that, but it's a lot of plumbing...
If there is no serious objection, I'd like to go ahead with this version,
Philip Guenther wrote:
> On Wed, Jun 1, 2016 at 10:37 AM, Theo de Raadt
> wrote:
> >> Mark Kettenis wrote:
> >> > I sympathise with the idea, but your implementation would still print
> >> > "funny" times if your machine had been up for more than a day.
> >>
> >> The perils of rebooting. I tested
On Wed, Jun 1, 2016 at 10:37 AM, Theo de Raadt wrote:
>> Mark Kettenis wrote:
>> > I sympathise with the idea, but your implementation would still print
>> > "funny" times if your machine had been up for more than a day.
>>
>> The perils of rebooting. I tested with an hour, then bumped to a day fo
Mark Kettenis wrote:
> I sympathise with the idea, but your implementation would still print
> "funny" times if your machine had been up for more than a day.
The perils of rebooting. I tested with an hour, then bumped to a day for
margin. But really, I think even up to ten years would work. Any "d
> Mark Kettenis wrote:
> > I sympathise with the idea, but your implementation would still print
> > "funny" times if your machine had been up for more than a day.
>
> The perils of rebooting. I tested with an hour, then bumped to a day for
> margin. But really, I think even up to ten years would
> From: "Ted Unangst"
> Date: Tue, 31 May 2016 21:46:16 -0400
>
> Small timespecs print funny:
>
> 57686 chrome CALL clock_gettime(CLOCK_MONOTONIC,0x7f7f0028)
> 57686 chrome STRU struct timespec { 15411<"Dec 31 23:16:51
> 1969">.584609082 }
> 57686 chrome RET clock_gettime 0
>
Small timespecs print funny:
57686 chrome CALL clock_gettime(CLOCK_MONOTONIC,0x7f7f0028)
57686 chrome STRU struct timespec { 15411<"Dec 31 23:16:51 1969">.584609082
}
57686 chrome RET clock_gettime 0
57686 chrome CALL clock_gettime(CLOCK_MONOTONIC,0x7f7eff48)
57686 chrom
