Riverbed Cascade Pilot Personal Edition: Take Wireshark to the Next Level - Advanced Triggers and Alerts; Web and VoIP Analytics; Long-Term Trending and Forensics; Deep Packet Analysis with Wireshark

Wireshark-dev: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds

Date Index Thread Index Other Months All Mailing Lists

Date Prev Date Next Thread Prev Thread Next

From: Stig Bjørlykke <stig.bjorlykke@xxxxxxxxx>
Date: Mon, 3 Dec 2007 21:14:17 +0100

Hi.

We currently have a problem drawing advanced time graphs when the timevalue is greater than ~429 seconds. This is because we handle secondsand microseconds in one guint32, which will wrap at this point.


Do all platforms support guint64 or should we stay with this limit?
Or maybe rewrite gtk/io_stat.c to handle time differently?


--
Stig Bjørlykke

Follow-Ups:
- Re: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds
  - From: Jeff Morriss

Prev by Date: Re: [Wireshark-dev] Make --with-ssl default?
Next by Date: Re: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds
Previous by thread: [Wireshark-dev] Wiretap module ("file_format") plugin
Next by thread: Re: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds
Index(es):
- Date
- Thread