Wireshark-bugs: [Wireshark-bugs] [Bug 1056] Timestamping seems to be broken
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sun, 20 May 2007 11:25:16 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1056





------- Comment #5 from sake@xxxxxxxxxx  2007-05-20 11:25 GMT -------
Created an attachment (id=681)
 --> (http://bugs.wireshark.org/bugzilla/attachment.cgi?id=681&action=view)
fix-bug1056.patch

This patch fixes the incorrect behaviour when the first frame of in a
packet-capture has absolute time epoch. I added two fucntions as follows to
determine if a frame is the first frame:

/* set the given nstime_t to (0,maxint) to mark it as "unset"
 * That way we can find the first frame even when a timestamp
 * is zero (fix for bug 1056)
 */
extern void nstime_set_unset(nstime_t *nstime);

/* is the given nstime_t currently (0,maxint)? */
extern gboolean nstime_is_unset(nstime_t *nstime);

Cheers,   Sake


-- 
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.