First Wireshark bug report, please be gentle.
I had a copy of Wireshark 1.6.2 installed and working for a long time.
Today I upgraded to 1.6.6; now, Wireshark crashes when it launches.
The latest nightly rebuild also crashes when it loads, in the same
module. It appears to be complaining about libgcrypt-11, but I'm not a
programmer.
wireshark 1.7.1-SVN-41818 (SVN Rev 41818 from /trunk)
Copyright 1998-2012 Gerald Combs <gerald@xxxxxxxxxxxxx> 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 GTK+ 2.22.1, with Cairo 1.10.2, with Pango 1.28.3, with
GLib 2.26.1, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS
2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with PortAudio
V19-devel (built Mar 28 2012), with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 21022
This is the default Windows crash info; is there a way I can gather
more useful debugging info, or is this already a known issue?
Problem signature:
Problem Event Name: APPCRASH
Application Name: wireshark.exe
Application Version: 1.7.1.41818
Application Timestamp: 4f72ffde
Fault Module Name: libgcrypt-11.dll
Fault Module Version: 17.6.0.1438
Fault Module Timestamp: 4f6bd206
Exception Code: c0000005
Exception Offset: 0000000000013b6b
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 40a0
Additional Information 2: 40a06ae317fe91f0cc8e1dc3f3f06302
Additional Information 3: b0f0
Additional Information 4: b0f072aff2d05455f4a5d5c0dc70ce9b
--
deny ip any any (4393649193 matches)