http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1886
Summary: Conversation exposes "Dissector bug, protocol NCP"
Product: Wireshark
Version: SVN
Platform: All
OS/Version: All
Status: NEW
Severity: Major
Priority: Medium
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: jyoung@xxxxxxx
Build Information:
Version 0.99.7-SVN-23035 (SVN Rev 23035)
Copyright 1998-2007 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 with GTK+ 2.12.0, with GLib 2.14.1, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with SMI 0.4.5, with ADNS, with Lua 5.1,
with
GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio PortAudio
V19-devel, with AirPcap.
Running on Windows XP Service Pack 1, build 2600, with WinPcap version 4.0.1
(packet.dll version 4.0.0.901), based on libpcap version 0.9.5, without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
With a specific NCP trace file loaded, selecting Wireshark's menu item
"Statistics" -> "Conversations" can result in MS Window's based Wireshark to
crash, and Linux based Wireshark to seg fault. Under Windows, if one has
enabled the Wireshark Debug Console ("Edit" -> "Preferences..." -> "Open a
console window") then the following error message will be written into the
console window (whether or not Wireshark itself actually crashes):
> 22:43:07 Warn Dissector bug, protocol NCP, in packet 2: STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address
The message above has been seen as far back as 0.99.4pre1 (SVN 19648)
(~2006-10-20). This problem appears to have been introduced sometime after
0.99.3-SVN-18786 (~2006-07-22) which did NOT generate the message above.
I will attach a small 2 frame trace which can be used to recreate the problem.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.