Bug 108841

Summary: Zdump prints bad information and hangs
Product: Base System Reporter: Derek Tattersall <dlt>
Component: amd64Assignee: freebsd-amd64 (Nobody) <amd64>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Derek Tattersall 2007-02-06 17:00:35 UTC 
zdump -v EST5EDT prints 4 records as follows:
[dlt@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"
Comment 1 Vasil Dimov freebsd_committer freebsd_triage 2007-02-28 08:08:04 UTC 
State Changed
From-To: open->closed

Superseded by amd64/109584