Wireshark-dev: Re: [Wireshark-dev] can't filter field in wireshark
thanks for your response....
However, what you said is very importanty
for me because I have put this function in many place of my code !!!!
Is there any other function that can
replace the "proto_tree_add_text()"
??
and do you think that it exist a way
to satisfy my question in the precedent mail ???
regards
De :
Chris Maynard <Chris.Maynard@xxxxxxxxx>
A :
wireshark-dev@xxxxxxxxxxxxx
Date :
18/08/2011 15:57
Objet :
Re: [Wireshark-dev]
can't filter field in wireshark
Envoyé par :
wireshark-dev-bounces@xxxxxxxxxxxxx
<Moussa.Alawieh@...> writes:
> I put the result in Wireshark with the
> "proto_tree_add_text"
> function, but it's impossible
> to filter this field because it's a text !!!!!
> can someone help-me ???
> regards
Don't use proto_tree_add_text(). To quote doc/README.developer:
proto_tree_add_text() is used to add a label to the GUI tree. It
will
contain no value, so it is not searchable in the display filter process.
This function was needed in the transition from the old-style proto_tree
to this new-style proto_tree so that Wireshark would still decode all
protocols w/o being able to filter on all protocols and fields.
Otherwise we would have had to cripple Wireshark's functionality while
we
converted all the old-style proto_tree calls to the new-style proto_tree
calls. In other words, you should not use this in new code unless
you've got
a specific reason (see below).
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe