Wireshark-bugs: [Wireshark-bugs] [Bug 5333] New: SEG Fault when adding new filetype to read - wi

Date: Fri, 22 Oct 2010 16:48:16 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5333

           Summary: SEG Fault when adding new filetype to read - wiretap
           Product: Wireshark
           Version: SVN
          Platform: x86
        OS/Version: Debian
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Extras
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: alindber@xxxxxxxxx


Alex Lindberg <alindber@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #5364|                            |review_for_checkin?
               Flag|                            |

Created an attachment (id=5364)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5364)
Diff and file set to demonstrate Seg fault

Build Information:
TShark 1.5.0 (SVN Rev 34625 from /trunk)

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 (32-bit) with GLib 2.24.2, with libpcap 1.1.1, with libz 1.2.3.4, with
POSIX capabilities (Linux), without libpcre, with SMI 0.4.8, with c-ares 1.7.3,
with Lua 5.1, without Python, with GnuTLS 2.8.6, with Gcrypt 1.4.5, with MIT
Kerberos, with GeoIP.

Running on Linux 2.6.32-5-686, with libpcap version 1.1.1, with libz 1.2.3.4.

Built using gcc 4.4.5.

--
Adding a new filetype to read in wiretap results in a seg fault while the
file_gets is run.

Attached are the svn diff of wiretap/ and the files mynewfiletype.[ch]. 

The files are not complete but they demonstrate that the simple act of reading
a line from the file causes a seg fault.

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