Wireshark-dev: Re: [Wireshark-dev] Different wireshark behaviour on Linux as on Windows
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Chris Maynard <Chris.Maynard@xxxxxxxxx>
Date: Tue, 8 Mar 2011 03:41:45 +0000 (UTC)
Roland Knall <rknall@...> writes:

> Ok, now I have a question.
> 
> Both dissectors register on a certain Ethernet Frame Type (0x88CD). If
> I disable the SercosIII dissector, in theory, my dissector should get
> called, right?
That would be my expectation as well.

> But no, even if I specifically disable the dissector, it still get's
> selected via packet.c::dissector_try_uint_new but it get's not called.
> 
> Is this a bug? Normally I would assume, that a disabled dissector
> would not get selected here, but a non-disabled one would get the
> top-vote
This sounds like a bug to me as well.  You might want to file a bug report about
it, and if at all possible, post your openSAFETY plugin (with the rest of the
patches to Wireshark files), along with a small capture file to the bug report.

The only other thing I could suggest is to compile your dissector as a normal
dissector instead of a plugin.  Does it need to be a plugin?