Wireshark-bugs: [Wireshark-bugs] [Bug 3816] New: TShark and fuzz-test do not detect dissector as
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 7 Aug 2009 01:29:10 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3816

           Summary: TShark and fuzz-test do not detect dissector asserts
           Product: Wireshark
           Version: 1.2.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: TShark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: joan@xxxxxxxxx


Build Information:
TShark 1.2.0 (SVN Rev 25444)

Copyright 1998-2009 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 GLib 2.16.2, with libpcap 0.9.8, with libz 1.2.3, without POSIX
capabilities, with libpcre 7.6, with SMI 0.4.5, without c-ares, with ADNS,
without Lua, without GnuTLS, without Gcrypt, without Kerberos, without GeoIP.

Running on Linux 2.6.24.7-laptop-2mnb, with libpcap version 0.9.8.

Built using gcc 4.2.3 (4.2.3-6mnb1).

--
TShark and fuzz-test.sh don't detect dissector asserts.

The reason is that TShark shows nothing when a dissector assert fails
(DISSECTOR_ASSERT). It should show a similar text as Wireshark does:

09:33:13          Warn Dissector bug, protocol 104asdu, in packet 917:
packet-iec104.c:1109: failed assertion "..."

'fuzz-test.sh' uses TShark and searches for 'dissector bug' in the output. So,
if TShark is fixed, fuzz-test will detect dissector asserts.


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