| Bug ID |
11524
|
| Summary |
Qt Wireshark - Follow TCP stream fails: Error: The packets in the capture file for that stream have no data.
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
x86
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.99.10-JYBUILD (v1.99.10rc0-99-gb4e972b from unknown)
Copyright 1998-2015 Gerald Combs <[email protected]> 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.4.1, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, without PortAudio,
with AirPcap.
Running on 64-bit Windows 8.1, build 9600, with locale C, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz (with SSE4.2), with 3980MB of physical
memory.
Built using Microsoft Visual C++ 12.0 build 31101
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Attempts to use the Follow TCP Stream feature results in an Error dialog with
the message "Error: The packets in the capture file for that stream have no
data."
Attempts to use the Follow UDP Stream feature simply opens the Follow Stream
dialog but display 0 client and 0 server packets.
Problem was seen with current buildbot images on both OS X and Windows systems.
Used git bisect to identify when problem started:
> C:\Development\wireshark>git bisect bad
> b4e972b7297b8835cacfc7ded7170de96140ce37 is the first bad commit
You are receiving this mail because:
- You are watching all bug changes.