https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14352

            Bug ID: 14352
           Summary: Binary dissector is not loaded with current git
                    master, despite being in correct directories
           Product: Wireshark
           Version: Git
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: Normal
          Priority: Low
         Component: Dissection engine (libwireshark)
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: tgp...@gmail.com
  Target Milestone: ---

Build Information:
Wireshark 2.5.0 (v2.5.0rc0-2398-gd86f8202)

Copyright 1998-2018 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.10.0, with libpcap, with POSIX capabilities
(Linux),
with libnl 3, with GLib 2.54.0, with zlib 1.2.11, without SMI, with c-ares
1.13.0, with Lua 5.2.4, with GnuTLS 3.5.16, with Gcrypt 1.8.2, with MIT
Kerberos, with GeoIP, with nghttp2 1.28.0, with LZ4, with Snappy, with libxml2
2.9.7, with QtMultimedia, with SBC, with SpanDSP, without bcg729.

Running on Linux 4.14.9-1-ARCH, with Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
(with SSE4.2), with 15912 MB of physical memory, with locale en_US.utf8, with
libpcap version 1.8.1, with GnuTLS 3.5.16, with Gcrypt 1.8.2, with zlib 1.2.11,
binary plugins supported (0 loaded).

Built using gcc 7.2.1 20171128.

--
Overview:

I'm currently working on a dissector, updating it from 1.x to <=2.4 and as a
side mission I'm on it making it work with 2.5 to future proof it as much as
possible.

This is the dissector I'm trying to get working with 2.5:
https://github.com/iguessthislldo/OpenDDS/tree/wireshark2/tools/dissector

This is the where the protocol I'm focusing on is registered:
https://github.com/iguessthislldo/OpenDDS/blob/wireshark2/tools/dissector/packet-opendds.cpp

This is where I changed the version strings for 2.5:
https://github.com/iguessthislldo/OpenDDS/blob/wireshark2/tools/dissector/plugin.cpp

I built it against the git master last month and it crashed with wmem_scope.c
epan_scope() assert when registering expert info. Today I decided to pull the
latest and try again but it doesn't load now. It's not listed in the Plugins
dialog but doesn't give any error (In gui or stderr) when Wireshark starts. I
have tried placing the dissector in the plugins directory in the source and the
Global and Personal Directories listed in Wireshark Folders dialog, with and
without "2.5" directory.

Steps to Reproduce:

Reproducing this might be hard given it's part of such a large library, but I
will include them for completeness (assuming standard Linux):

1. Clone wireshark, checkout d86f8202067e3671d2039a315e1abbd8cd6f1db9 if that
is no longer HEAD, and build as normal.

2. Recursively clone OpenDDS from https://github.com/iguessthislldo/OpenDDS and
checkout d5c1672eaa8d674046cbddc8139ea56797cad9f3

3. In OpenDDS: run ./configure --wireshark <Location of Wireshark Source>
--rapidjson --glib

4. make -j <Number of threads>

5. Once that's built (It'll take a while) copy the OpenDDS_Dissctor.so file
from tools/dissector to a place that Wireshark is looking at. (like
~/.local/lib/wireshark/plugins/2.5).

6. Run Wireshark

Actual Results:

Wireshark starts as normal, but does not have my dissector in the list of
Plugins, and treats the OpenDDS packets as the underlying GIOP and TCP packets.

Expected Results:

Wireshark lists the plugin in the list of Plugins and dissects the associated
packets.

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to