Ethereal-dev: Re: [Ethereal-dev] patch to M3UA to call MTP3 dissector even when !tree
Guy,
thank you very much. I used a display filter which never matched
in the testcases. Now I know how to test the stuff.
Best regards
Michael
On Tuesday, Jan 28, 2003, at 00:16 Europe/Berlin, Guy Harris wrote:
On Tue, Jan 28, 2003 at 12:04:38AM +0100, Michael Tuexen wrote:
if I load my example file with the command given by you I DO see the
correct entry in the Info Column. I'm not using any Display filter.
Are you using any color filters (regardless of whether any of them
match
any packets in the capture)?
Are you using any taps?
It's not really an issue of display filters vs. no display filters,
it's
an issue of generating a protocol tree vs. not generating a protocol
tree - if a display filter is being used, a protocol tree is generated,
but that's also the case if a color filter, or a tap that does
filtering
or passes the protocol tree to the tap, is being used.
(BTW, there's a similar problem with the RFC 3332 version of M3UA -
"dissect_parameter()" returns immediately if "tree" is null, even if
the
parameter is "Protocol data". I'll check in a fix.)
