Bug#412569: libc6: zdump -v segfaults

[Kurt Roeckx <kurt@roeckx.be>]

So on amd64, with 2.3.2.ds1-22sarge4 I get:
intrepid:~$ zdump -v /usr/share/zoneinfo/UTC
/etc/localtime  -9223372036854775808 = NULL
/etc/localtime  -9223372036854689408 = NULL
/etc/localtime  9223372036854689407 = NULL
/etc/localtime  9223372036854775807 = NULL
intrepid:~$ zdump --version
@(#)zdump.c     7.64

Upgrading to 2.3.2.ds1-22sarge5 I get:
intrepid:~$ zdump -v /usr/share/zoneinfo/UTC
Segmentation fault
intrepid:~$ zdump --version
zdump: invalid option -- -
zdump: usage is zdump [ -v ] [ -c cutoff ] zonename ...

I think it broke on 64 bit arches.

With 2.3.6.ds1-13 (unstable) I still get:
intrepid:~$ zdump -v /usr/share/zoneinfo/UTC
/etc/localtime  -9223372036854775808 = NULL
/etc/localtime  -9223372036854689408 = NULL
/etc/localtime  9223372036854689407 = NULL
/etc/localtime  9223372036854775807 = NULL
intrepid:~$ zdump  --version
@(#)zdump.c     7.66


On i386 I get:
intrepid:~$ zdump -v /usr/share/zoneinfo/UTC
/etc/localtime  Fri Dec 13 20:45:52 1901 UTC = Fri Dec 13 20:45:52 1901 UTC isdst=0 gmtoff=0
/etc/localtime  Sat Dec 14 20:45:52 1901 UTC = Sat Dec 14 20:45:52 1901 UTC isdst=0 gmtoff=0
/etc/localtime  Mon Jan 18 03:14:07 2038 UTC = Mon Jan 18 03:14:07 2038 UTC isdst=0 gmtoff=0
/etc/localtime  Tue Jan 19 03:14:07 2038 UTC = Tue Jan 19 03:14:07 2038 UTC isdst=0 gmtoff=0

On amd64, it never seems to show 1901 / 2038 properly.  If I use a
different timezone, and not using 2.3.2.ds1-22sarge5 the first 2 and
last lines still look the same, but the rest between them look normal.


Kurt