| Bug ID |
11972
|
| Summary |
Crash with snooping NFS file handles
|
| Product |
Wireshark
|
| Version |
2.0.1
|
| Hardware |
x86
|
| OS |
Windows Server 2008 R2
|
| Status |
CONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.0.1 (v2.0.1-0-g59ea380 from master-2.0)
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.3.2, 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, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows Server 2008R2 Service Pack 1, build 7601, with
locale
C, without WinPcap, with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Six-Core AMD Opteron(tm) Processor 2431, with 65533MB 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.
--
Hello Wireshark Developer,
the current version of Wireshark crashes if snooping NFS filehandles is
enabled.
I would share the pcap file to reproduce the issue within a private email.
Steps to reproduce:
1. Delete existing wireshark profile e.g. C:\Users\<your
username>\AppData\Roaming\Wireshark
2. Load attached pcap file "crash_nfs_snoop_fh.pcap"
3. Open NFS protocol preferences and select "Snoop FH to filename mappings" and
"Snoop full path to filenames"
4. Sometime Wireshark crashes immediately, sometimes during an immediate exit
5. Open pcap file again and check protocol preferences if both snoop settings
are selected
6. Wireshark crashes on exit again
The old version 1.12.8 is not affected.
Regards,
Carsten
You are receiving this mail because:
- You are watching all bug changes.