Wireshark-bugs: [Wireshark-bugs] [Bug 12616] `tshark -T fields -e data` crashes in versions afte
Comment # 7
on bug 12616
from Miroslav Rovis
(In reply to Jeff Morriss from comment #6)
> (In reply to Miroslav Rovis from comment #2)
> > > and tshark gets only garbage or very incomplete stubs of, or empty data
> > > instead of SSL streams either raw, as above, or ascii (pls see the
> > > tshark-streams.sh in the linked github page for that). With, I think also
> > > wireshark-2.0.4, but tested and always reproducible here, with
> > > wireshark-2.0.6.
> > >
> > It is in wireshark-2.1.0 that I can always reproduce it and that I tested
> > it in.
>
> Just to clarify: I can't reproduce the problem in the master-2.0 branch (so:
> the latest 2.0.x release). The submitted change fixes things in master
> (2.1.x and subsequently 2.2.0) but doesn't apply to the 2.0.x releases.
And it's the opposite here. I can't get it to work with your fix in:
$ tshark -v
TShark (Wireshark) 2.1.1-git (v2.1.1rc0-522-g6c0972b from master)
Copyright 1998-2016 Gerald Combs <gerald@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 libpcap, with POSIX capabilities (Linux), with libnl 3,
with GLib 2.48.1, with zlib 1.2.8, with SMI 0.5.0, without c-ares, with Lua
5.1,
with GnuTLS 3.4.14, with Gcrypt 1.7.1, without Kerberos, without GeoIP.
Running on Linux 4.5.7-hardened-r7-160710, with locale en_GB.utf8, with libpcap
version 1.7.4, with GnuTLS 3.4.14, with Gcrypt 1.7.1, with zlib 1.2.8.
AMD Phenom(tm) II X4 965 Processor
Built using gcc 5.4.0.
( By the book --
https://www.wireshark.org/docs/wsdg_html_chunked/ChSrcBuildFirstTime.html#_building_on_unix
-- And that is the third try. Previous two were via Gentoo Portage system.
> So: none of the 2.0.x releases should have this exact problem. Of course
> they may have another problem that has the same symptoms. If you do see
> such a problem in the 2.0.x versions please let us know.
It could be something else, then. I believe it would be better for me to try
and tell more (since I'm less than or only a beginner programmer) on the thread
linked above on the mailing list, so we can see what this really is.
You are receiving this mail because:
- You are watching all bug changes.
