Wireshark-bugs: [Wireshark-bugs] [Bug 7029] New: Segfault when processing ospf.advrouter custom
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 3 Apr 2012 10:07:42 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7029

           Summary: Segfault when processing ospf.advrouter custom column
           Product: Wireshark
           Version: SVN
          Platform: x86
        OS/Version: Mac OS X 10.6
            Status: NEW
          Severity: Major
          Priority: Low
         Component: TShark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: jyoung@xxxxxxx


Build Information:
TShark 1.7.1-SVN-41895 (SVN Rev 41895 from /trunk)

Copyright 1998-2012 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 GLib 2.29.8, with libpcap, with libz 1.2.3, without
POSIX
capabilities, with SMI 0.4.8, without c-ares, without ADNS, with Lua 5.1,
without Python, with GnuTLS 2.12.7, with Gcrypt 1.4.6, with MIT Kerberos, with
GeoIP.

Running on Mac OS 10.6.8 (Darwin 10.8.0), with locale en_US.UTF-8, with libpcap
version 1.0.0, with libz 1.2.3.

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

--
Tshark will segfault when processing an ospf.advrouter custom column field when
there are "too many" items in the field.

The following tshark command will trigger the segfault with the attached one
packet tracefile: 

tshark -r ospf-lsa.pcap -o 'column.format: "Advertising Router",
"%Cus:ospf.advrouter:0:R"'

The following tshark command will allow one to see the all 49 items in the
"ospf.advrouter" field:

tshark -r ospf-lsa.pcap -T fields -e ospf.advrouter

I haven't had any time to look at source, but I suspect this problem may NOT be
limited to just the ospf.advrouter field but for any custom column that might
contain "too many" items.

This same custom column definition will sometimes trigger Wireshark to crash
although not as reliably and sometimes not at all.  To crash Wireshark I had to
try to manipulate the column (sort on the column, try to widen or narrow the
column, or click in a "cell" within the column).

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