Wireshark-bugs: [Wireshark-bugs] [Bug 6994] New: IO Graph LOAD inaccuracy, intervals not display

Date: Sat, 24 Mar 2012 10:16:01 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6994

           Summary: IO Graph LOAD inaccuracy, intervals not displayed,
                    wrong frames displayed
           Product: Wireshark
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: turney_cal@xxxxxxx


Created attachment 8079
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=8079
Patches for the 3 bugs

Build Information:
Version 1.7.2-41324-iostat (SVN Rev Unknown from unknown)

Copyright 1998-2012 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (32-bit) with GTK+ 2.24.10, with Cairo 1.10.2, with Pango 1.29.4, with
GLib 2.28.8, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS
2.10.3, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Mar  3 2012), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 10.0 build 40219
-----------------------------------------------------------------------------



--
(Note: The analogous issues in tshark's io,stat in bugs 1 and 2 below were
reported and fixed in Bug 6883.)

Bug #1:  The LOAD stat in the last row of the tshark output and last column of
the Wireshark dialog is incorrect because rpc.time is divided by the full
interval rather than limiting the interval to the capture duration. 

Bug #2:  Intervals at the end of capture for which there is no data are not
displayed. 

Bug #3: When LOAD is selected and the user clicks an interval that does not
contain a response, the first frame of the next interval with a response minus
one is displayed. If there are gaps with no responses, a completely irrelevant
frame is selected.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.