FW: zic and zoneinfo.zip

Dominique Pellé dominique.pelle at gmail.com
Mon Sep 27 16:34:16 UTC 2010

Olson, Arthur David (NIH/NCI) [E] <olsona at dc37a.nci.nih.gov> wrote:

> I'm forwarding this message from Ravindra, who is not on the time zone mailing list. Those of you who are on the list, please direct replies appropriately.
> (Note that the line numbers below are indeed different from those in the 2010l on elsie.nci.nih.gov, and that there's no "tz.c" file with a "tz_validate" function in 2010l on elsie.nci.nih.gov.)
>                                --ado
> -----Original Message-----
> From: Ravindra [mailto:rsahlot at yahoo.com]
> Sent: Saturday, September 25, 2010 8:01
> To: Olson, Arthur David (NIH/NCI) [E]
> Subject: RE: zic and zoneinfo.zip
> Thanks Arthur!
> Is there a place where I get pre-built zic binary for Linux?
> I got the doubt because I could build 32-bit zic as well as 64-bit zic from source code, and I was not sure whether to build zic as a 32-bit binary or 64-bit binary. What I'm getting from your response is I can use either version of zic and use the generated timezone data files on either platform.
> BTW, I'm looking at various possibilities because I'm using the code and data from version "2010l" and I'm hitting following memory error in valgrind log:
> ==5207== Thread 27:
> ==5207== Conditional jump or move depends on uninitialised value(s)
> ==5207==    at 0x1B9F988: typesequiv (localtime.c:522)
> ==5207==    by 0x1B9F830: tzload (localtime.c:493)
> ==5207==    by 0x1BA261B: tz_validate (tz.c:1717)

For this kind of Valgrind error, you can get more information
if you rerun with valgrind option  --track-origins=yes
(default being no). This option is only available in recent
valgrind versions (>= 3.5 I think).

It should help to find the root cause of the issue.

-- Dominique

More information about the tz mailing list