Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 6503] New: Wireshark crashes if a field of type BASE_CUSTO

Date: Thu, 27 Oct 2011 06:07:51 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6503

           Summary: Wireshark crashes if a field of type BASE_CUSTOM is
                    applied as a column
           Product: Wireshark
           Version: 1.6.2
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: wireshark@xxxxxxxxxxxxxxx


Build Information:
Version 1.6.2

Copyright 1998-2011 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 (32-bit) with GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3,
with
Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Oct
25 2011), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, 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.10.3, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Wireshark crashes if a field of type BASE_CUSTOM is applied as a column.

I have seen the same crash in a proprietary dissector with a BASE_CUSTOM field.

To reproduce this issue:
* open the .pcap file attached to bug 4319, go to frame 432
* expand the groups: Data, Tracking,
* select the item "Channel", right click and "Apply as column"

the result is an exception: Unhandled exception at 0x68610986 in wireshark.exe:
0xC0000005: Access violation reading location 0x94682deb.

The code at the point where the debugger breaks appears (to me) to be not
directly related to the crash.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.