Comment # 3
on bug 8197
from Evan Huus
(In reply to comment #2)
> I could have trunk-1.8 top of tree crash with this capture when doing a
> tshark -nVr on the capture.
That's very strange - I'm not seeing any such errors. I have removed my
~/.wireshark directory to ensure I am starting with a default profile. My build
information is as follows:
TShark 1.8.5 (SVN Rev 47055 from /trunk-1.8)
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 (64-bit) with GLib 2.34.3, with libpcap, with libz 1.2.7, with POSIX
capabilities (Linux), with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without
Python, with GnuTLS 2.12.20, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP.
Running on Linux 3.8.0-0-generic, with locale en_CA.UTF-8, with libpcap version
1.3.0, with libz 1.2.7.
Built using gcc 4.7.2.
> A trunk Wireshark also triggers an error, but in another dissector (ASN.1
> BER and not PER if I remember correctly, but I might be wrong).
> I did not have the time to investigate at all.
I'm also not seeing this one. I wonder what's wrong with my setup?
You are receiving this mail because:
- You are watching all bug changes.
