http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2251
Summary: at midnight the trace date jumps forward
Product: Wireshark
Version: 0.99.7
Platform: PC
OS/Version: Windows 2000
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: martinstrud@xxxxxxxxx
Build Information:
Version 0.99.7 (SVN Rev 23910)
Copyright 1998-2007 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled with GTK+ 2.12.1, with GLib 2.14.3, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with SMI 0.4.5, with ADNS, with Lua 5.1,
with
GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio PortAudio
V19-devel, with AirPcap.
Running on Windows 2000 Service Pack 4, build 2195, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
I have created a trace via the IBM z/OS V1.4 Component trace facility. This
trace is bin transferred via FTP to my desktop as a .cap file and then openned
with Wireshark. The trace data spans midnight, but the display time
information jumps. For instance in yesterdays trace my time stamp went from
2008-02-06 23:59:52 the next entry was 2008-03-02 10:50:46. Todays trace also
did the same thing at midnight, consecutive records went from 2008-02-07
23:59:53 to 2008-03-03 10:50:46. When I view these records via the IPCS
analyzer under z/OS the records show with correct time stamps.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.