Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9780] New: tshark -z follow stops after missing or broken package

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	9780
Summary	tshark -z follow stops after missing or broken package
Classification	Unclassified
Product	Wireshark
Version	unspecified
Hardware	x86
OS	Windows 7
Status	UNCONFIRMED
Severity	Major
Priority	Low
Component	TShark
Assignee	bugzilla-admin@wireshark.org
Reporter	tonivalac@web.de

Build Information:
TShark 1.10.1 (SVNRev 50926 from /trunk-1.10)

Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> 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 GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5,
without POSIX capabilities, without libnl, with SMI 0.4.8, with c-ares 1.9.1,
with Lua 5.1, without Python, with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT
Kerberos, with GeoIP.

Running on 64-bit Windows 7 Service Pack 1, build 7601, without WinPcap.
Intel(R) Core(TM)2 Duo CPU     E7400  @ 2.80GHz, with 4029MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219

--
Using "tshark -z 'follow,tcp,ascii,<stream number>'" stops whenever the stream
contains a broken or missing package. For example if a txt file was
transmitted, but some package could not be recieved by the device captured on
by wireshark and tshark is then fed the pcap file with the described command,
it stops right after the package before the missing one.

However, using wireshark, I can clearly see, that more data of the file was
captured and also correctly assigned to the tcp stream. I noticed this bug in
all wireshark/tshark versions I used so far and both on Linux and Windows. The
bug affects also wiresharks "follow tcp stream" option.

Please help me and help me quick, because I need this working VERY badly.

---

      You are receiving this mail because:

• You are watching all bug changes.