Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [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: Jeff Morriss <jeff.morriss.ws@xxxxxxxxx>
Date: Mon, 03 Dec 2007 15:16:17 -0500



Stig Bjørlykke wrote:
Hi.

We currently have a problem drawing advanced time graphs when the time value is greater than ~429 seconds. This is because we handle seconds and 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?

Wireshark has required the support of guint64 for a while now--that's a safe way to go.

  • Follow-Ups:
    • Re: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds
      • From: Stig Bjørlykke
  • References:
    • [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds
      • From: Stig Bjørlykke
  • Prev by Date: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds
  • Next by Date: Re: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds
  • Previous by thread: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds
  • Next by thread: Re: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation