amd64/108841: Zdump prints bad information and hangs

[Derek Tattersall]

>Number:         108841
>Category:       amd64
>Synopsis:       Zdump prints bad information and hangs
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb 06 17:00:35 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator:     Derek Tattersall
>Release:        7.0-current
>Organization:
>Environment:
FreeBSD nebbish.arm.org 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Feb  2 13:23:47 EST 2007     root at nebbish.arm.org:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
zdump -v EST5EDT prints 4 records as follows:
[dlt at nebbish 536 zdump]$ zdump -v EST5EDT
EST5EDT  Sun Jan 26 08:29:52 -219 UTC = Sun Jan 26 03:29:52 -219 EST isdst=0 gmtoff=-18000
EST5EDT  Mon Jan 27 08:29:52 -219 UTC = Mon Jan 27 03:29:52 -219 EST isdst=0 gmtoff=-18000
EST5EDT  Fri Jan  1 04:59:59 -219 UTC = Thu Dec 30 23:59:59 -219 EST isdst=0 gmtoff=-18000
EST5EDT  Fri Jan  1 05:00:00 -219 UTC = Fri Jan  1 00:00:00 -219 EST isdst=0 gmtoff=-18000

Then hangs.  Can be killed by ctrl-c.  I found that the localtime() call in show() 
returns incorrect information in at least the year field.
>How-To-Repeat:
execute from a command prompt "zdump -v EST5EDT"
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: