https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12476

            Bug ID: 12476
           Summary: IO graph not displaying HTTP.time in graph correctly
           Product: Wireshark
           Version: 2.0.3
          Hardware: x86
                OS: Mac OS X 10.11
            Status: UNCONFIRMED
          Severity: Normal
          Priority: Low
         Component: GTK+ UI
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: allc...@gmail.com

Build Information:
Wireshark 2.0.3 (v2.0.3-0-geed34f0 from master-2.0)

Copyright 1998-2016 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 (64-bit) with Qt 5.3.2, with libpcap, without POSIX capabilities, with
libz 1.2.5, with GLib 2.36.0, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2,
with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP, with
QtMultimedia, without AirPcap.

Running on Mac OS X 10.11.3, build 15D21 (Darwin 15.3.0), with locale C, with
libpcap version 1.5.3 - Apple version 54, with libz 1.2.5, with GnuTLS 2.12.19,
with Gcrypt 1.5.0.
       Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (with SSE4.2)

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).

--
When working with IO graphs using http.time or http.time > 1 the graph does not
correctly find the correct packets. This was also tested on Wireshark version
1.12.11 and works with no issues.

Regards,
JB

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to