Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 1056] Timestamping seems to be broken

Date: Wed, 30 Aug 2006 10:20:43 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1056


dgautheron@xxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dgautheron@xxxxxxxx




------- Comment #4 from dgautheron@xxxxxxxx  2006-08-30 10:20 GMT -------
(In reply to comment #3)
> Created an attachment (id=349)
 --> (http://bugs.wireshark.org/bugzilla/attachment.cgi?id=349&action=view) [edit]
> A smaller trace exposing the same behavior
> 
It's zero the culprit. Wireshark uses it as a magic value for no value, cf
file.c.

A quick workaround would be to use MAXINT or whatever is the maximum value for
time_t. If you have MAXINT in your timestamp Wireshark is already broken
anyway.


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.