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: Stig Bjørlykke <stig.bjorlykke@xxxxxxxxx>
Date: Mon, 3 Dec 2007 21:56:43 +0100

On 3. des.. 2007, at 21.16, Jeff Morriss wrote:

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

And then the next question:
What to do with this GUINT_TO_POINTER when yscale_max changes to guint64?

OBJECT_SET_DATA(menu_item, "yscale_max", GUINT_TO_POINTER(yscale_max[i]));


--
Stig Bjørlykke



  • Follow-Ups:
    • Re: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds
      • From: Guy Harris
  • References:
    • [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds
      • From: Stig Bjørlykke
    • Re: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds
      • From: Jeff Morriss
  • Prev by Date: Re: [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: Re: [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