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 5039] New: Wireshark crashes when 'Apply as Column' is sel

Date: Wed, 21 Jul 2010 02:23:45 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5039

           Summary: Wireshark crashes when 'Apply as Column' is selected
                    on a boolean field
           Product: Wireshark
           Version: SVN
          Platform: x86
        OS/Version: Red Hat
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: jjk@xxxxxxx


Build Information:
wireshark 1.5.0

Copyright 1998-2010 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.10.4, (64-bit) with GLib 2.12.3, with libpcap 0.9.4, with
libz 1.2.3, with POSIX capabilities (Linux), with libpcre (version unknown),
with SMI 0.4.5, without c-ares, without ADNS, without Lua, without Python, with
GnuTLS 1.4.1, with Gcrypt 1.2.4, with MIT Kerberos, without GeoIP, without
PortAudio, without AirPcap.

Running on Linux 2.6.18-128.el5, with libpcap version 0.9.4, with libz 1.2.3,
GnuTLS 1.4.1, Gcrypt 1.2.4.

Built using gcc 4.1.2 20080704 (Red Hat 4.1.2-44).

--
Can be reproduced in thre easy steps:

- Open a capture file containing TCP packets
- Navigate to the flags field in a TCP packet
- Right-click on a flag and select 'Apply as Column'


The crash occurs as a result of an assertion failure in
hfinfo_numeric_value_format(), which doesn't currently handle FT_BOOLEAN
fields.

The column info is already saved in ~/.wireshark/preferences at the time of the
crash, which makes this particularly annoying...

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