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 5816] New: proto_field_is_referenced() is not exported in

Date: Sat, 9 Apr 2011 20:26:27 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5816

           Summary: proto_field_is_referenced() is not exported in
                    libwireshark.dll
           Product: Wireshark
           Version: 1.4.4
          Platform: All
        OS/Version: Windows XP
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: jttdi@xxxxxxxxx


Build Information:
wireshark 1.4.4 (SVN Rev 36110 from /trunk-1.4)

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 (32-bit) with GTK+ 2.16.6, with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, with
SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5,
with Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel
(built Mar 1 2011), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022
--
A plugin dissector on Windows XP cannot use the function
proto_field_is_referenced() declared in proto.h.

At plugin link time, an "unresolved external symbol _proto_field_is_referenced"
error is generated.

The libwireshark.def does not contain an entry for the
proto_field_is_referenced() function.  I believe that this function should be
available to plug-in dissectors so that they can make intelligent decisions
about continuing to dissect a frame only as much as necessary.

Not making this available means that plugin dissectors are guaranteed to hamper
the performance of Wireshark (at least on Windows).  (Of course, making it
available does not guarantee that it will be used.)

This bug applies to both tshark and wireshark.

I believe that this bug applies to any Windows platform (I filed on XP because
that is what I am using to build).

Should I not be using this function in a plug-in dissector?  It seems to work
well on Linux.

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