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 6028] New: Wireshark crashes when setting custom column's

Date: Thu, 16 Jun 2011 17:31:35 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6028

           Summary: Wireshark crashes when setting custom column's field
                    name with conditional
           Product: Wireshark
           Version: SVN
          Platform: x86-64
        OS/Version: Mac OS X 10.6
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: tony19@xxxxxxxxx


Build Information:
wireshark 1.7.0 (SVN Rev 37685 from /trunk)

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 (64-bit) with GTK+ 2.24.4, with GLib 2.28.7, with libpcap 1.0.0, with
libz 1.2.5, without POSIX capabilities, without libpcre, without SMI, without
c-ares, without ADNS, with Lua 5.1, with Python 2.6.1, without GnuTLS, without
Gcrypt, with MIT Kerberos, without GeoIP, without PortAudio, without AirPcap.

Running on Mac OS 10.6.7 (Darwin 10.7.0), with libpcap version 1.0.0, with libz
1.2.5.

Built using gcc 4.2.1 (Apple Inc. build 5666) (dot 3).

--
After setting a custom column's field name to a display-filter conditional, an
assertion failure occurs at
http://anonsvn.wireshark.org/viewvc/trunk/epan/column-utils.c?revision=36527&view=markup#l251


To reproduce:

1. Open a pcap file (to cause the crash after step 6)
2. Go to Preferences > User Interface > Columns
3. Click Add button
4. For "Field type", choose "Custom"
5. For "Field name", enter "ip.dst || ip.addr"
6. Click OK (or Apply) button
7. Observe the crash and the error message that prints on stdout

This also crashes in Ubuntu 11.04 and Windows XP SP3.


GDB backtrace:

**
ERROR:column-utils.c:251:col_custom_prime_edt: assertion failed: (hfinfo)

Program received signal SIGABRT, Aborted.
0x00007fff866c75d6 in __kill ()
(gdb) bt
#0  0x00007fff866c75d6 in __kill ()
#1  0x00007fff86767cd6 in abort ()
#2  0x00000001048431d8 in g_assertion_message ()
#3  0x0000000104843722 in g_assertion_message_expr ()
#4  0x00000001002fd9f5 in col_custom_prime_edt (edt=<value temporarily
unavailable, due to optimizations>, cinfo=<value temporarily unavailable, due
to optimizations>) at column-utils.c:251
#5  0x000000010006abce in packet_list_dissect_and_cache_record
(packet_list=0x105b06040, record=0x1095ae7b0, dissect_columns=1,
dissect_color=1) at packet_list_store.c:1180
#6  0x0000000100069aff in show_cell_data_func (col=<value temporarily
unavailable, due to optimizations>, renderer=0x105af9af0, model=<value
temporarily unavailable, due to optimizations>, iter=0x7fff5fbfee60, data=0x0)
at new_packet_list.c:1331
#7  0x0000000103da713b in gtk_tree_view_column_cell_set_cell_data ()
#8  0x0000000103d9f75a in validate_row ()
#9  0x0000000103d9ff5b in initialize_fixed_height_mode ()
#10 0x0000000103da06d8 in do_validate_rows ()
#11 0x0000000103da08ce in gtk_tree_view_size_request ()
#12 0x000000010479a6e2 in g_closure_invoke ()
#13 0x00000001047afdae in signal_emit_unlocked_R ()
#14 0x00000001047b1b08 in g_signal_emit_valist ()
#15 0x00000001047b1dd5 in g_signal_emit_by_name ()
#16 0x0000000103d0a8f8 in _gtk_size_group_compute_requisition ()
#17 0x0000000103da175a in do_presize_handler ()
#18 0x0000000103da2359 in presize_handler_callback ()
#19 0x0000000104074e89 in gdk_threads_dispatch ()
#20 0x000000010481d5a5 in g_main_context_dispatch ()
#21 0x00000001048212a2 in g_main_context_iterate ()
#22 0x00000001048215a5 in g_main_loop_run ()
#23 0x0000000103c99db0 in gtk_main ()
#24 0x0000000100053597 in main (argc=0, argv=0x7fff5fbff8a0) at main.c:2981

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