aboutsummaryrefslogtreecommitdiffstats
path: root/wiretap/wtap-int.h
diff options
context:
space:
mode:
authorGuy Harris <guy@alum.mit.edu>2008-02-10 18:29:05 +0000
committerGuy Harris <guy@alum.mit.edu>2008-02-10 18:29:05 +0000
commitc1e833bdefb9ebb80f9ae34d84d6e49fd4b6772c (patch)
treed721fc75ad16bb8c3141eda12e4a28109c77aacf /wiretap/wtap-int.h
parentbad9f18d338ee74dfa0d3c36c91c5929413f6348 (diff)
Do the time calculations with 64-bit integers, rather than in floating
point, so we don't have issues with numbers not being exactly representable; that makes it less likely that the change described below will change a time stamp if it's not fixing the time stamp (i.e., if time_day is 0). The Sniffer manual "Expert Sniffer(R) Network Analyzer Operations, Release 5.50" says that a frame2_rec has a time stamp with an 8-bit time_high field and an 8-bit time_day field. Interpreting the time stamp that way fixes the time stamps in at least some captures; see, for example, bug 2251. Fix/update some comments (for example, the Sniffer documentation is no longer at that URL). svn path=/trunk/; revision=24296
Diffstat (limited to 'wiretap/wtap-int.h')
-rw-r--r--wiretap/wtap-int.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/wiretap/wtap-int.h b/wiretap/wtap-int.h
index 807f93b25b..cd63fd937a 100644
--- a/wiretap/wtap-int.h
+++ b/wiretap/wtap-int.h
@@ -61,7 +61,7 @@ typedef struct {
typedef struct {
guint maj_vers;
guint min_vers;
- double timeunit;
+ guint32 timeunit;
time_t start;
guint network; /* network type */
ngsniffer_comp_stream_t seq; /* sequential access */