Re: Different wireshark behaviour on Linux as on Windows

[Roland Knall <rknall () gmail com>]

Hi

On Mon, Feb 28, 2011 at 9:55 AM, Roland Knall <rknall () gmail com> wrote:
> On Mon, Feb 28, 2011 at 9:51 AM, Guy Harris <guy () alum mit edu> wrote:

> > So my question is, can I influence the decision made by wireshark in
> > any way, which plugin get's called?
>
> Try disabling the dissector for the protocol whose dissector you don't want called.

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?

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

regards, Roland
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe