From: Ravindra [mailto:rsahlot@yahoo.com] Sent: Monday, September 27, 2010 8:09
More testing on this revealed that it happens only when I use tzdata from version "2010l" on a 64-bit platform (localtime.c compiled as 64-bit code). valgrind does not report the memory error if localtime.c is compiled as 32-bit code or if I use tzdata2007k with tzcode2010l.
I don't observe the problem with version 2010m on 64-bit RHEL with my GCC 4.5.1 installation. After running the following commands: wget ftp://elsie.nci.nih.gov/pub/tzcode2010m.tar.gz wget ftp://elsie.nci.nih.gov/pub/tzdata2010m.tar.gz tar xf tzcode2010m.tar.gz tar xf tzdata2010m.tar.gz make TOPDIR=`pwd`/topdir ALL install TZ=`pwd`/topdir/etc/zoneinfo/America/Los_Angeles valgrind ./date the output of the valgrind session is: ==723== Memcheck, a memory error detector ==723== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==723== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info ==723== Command: ./date ==723== Mon Sep 27 09:57:23 PDT 2010 ==723== ==723== HEAP SUMMARY: ==723== in use at exit: 0 bytes in 0 blocks ==723== total heap usage: 1 allocs, 1 frees, 1,024 bytes allocated ==723== ==723== All heap blocks were freed -- no leaks are possible ==723== ==723== For counts of detected and suppressed errors, rerun with: -v ==723== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)