[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 21 Nov 2013 11:39:11 -0500
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: Pending patches/issues before 0.9.15 release?
On Thu, Nov 21, 2013 at 09:40:57AM +0000, Laurent Bercot wrote:
> Hi Rich,
>
> I think there is a localtime bug related to
> http://www.openwall.com/lists/musl/2012/10/26/11
> but I've been unable to expose it in a reproducible way, and I
> haven't had time to investigate more.
Are you using the same source code from that email?
> But *once*, I got the following results :
>
> $ TZ=CEST ./localtime-musl ; TZ=CEST ./localtime-glibc
> Local: 06:13:34
> Global: 06:13:34 TUU
> Local: 06:13:34
> Global: 06:13:34
>
> $ TZ=:right/Europe/Paris ./localtime-musl ; TZ=:right/Europe/Paris ./localtime-glibc
> Local: 08:14:10
> Global: 06:14:10 TUU
> Local: 08:13:45
> Global: 06:13:45
>
> 1. That "TUU" looks like some random string is added after the time format, there
> seems to be a string length error.
Perhaps strftime is failing to null-terminate under some conditions.
Did you try pre-filling the buffer with junk to see if it makes the
bug reproducable?
> 2. There's a 35 second discrepancy between the glibc and musl results in the
> right/ case, which seems to indicate that musl prints UTC when it should print
> TAI-10. (This is reproducible.) Does musl support the A. D. Olson "right/" timezones ?
I'm not familiar with the "right/" timezones and they're difficult to
google for -- please give me a reference for what they are, if you
can. However, musl only uses zoneinfo for timezone/daylight-time
purposes, not for any sort of adjustment between POSIX/calendar time
and UTC(w/leap-seconds) and/or TAI. Perhaps this is the source of the
discrepency.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
