Thanks guys - works like a charm now...
Best regards,
Tobias
Original-Nachricht
> Datum: Sun, 15 Feb 2009 18:12:46 -0500
> Von: "Maynard, Chris"
> An: "Developer support list for Wireshark"
> Betreff: Re: [Wireshark-dev] Problem with proto_tr
ark.org [mailto:wireshark-dev-
> boun...@wireshark.org] On Behalf Of Tobias Erichsen
> Sent: Sunday, February 15, 2009 5:39 PM
> To: wireshark-dev@wireshark.org
> Subject: [Wireshark-dev] Problem with proto_tree_add_item...
>
> Hi everyone,
>
> I seem to have a little
2009/2/15 Tobias Erichsen :
> Has anyone possibly got any insights what I am doing wrong?
Use true_false_string and TFS instead of value_string and VALS for
boolean values.
--
Stig Bjørlykke
___
Sent via:Wireshark-dev m
Hi everyone,
I seem to have a little problem with calling proto_tree_add_item. On some
packets,
when I click on the entry to expand the tree, Wireshark crashes. If I don't
insert
those add_items, everything is fine...
Some sniplets of the code are below.
Has anyone possibly got any insights
Hi Guy,
I think this is a good solution.
This way I can avoid to write a parser function for each field name and can
keep the "type-parser".
Generating all the hf register entries is not a bidg deal.
thanks,
Gerhard.
On Thursday 01 February 2007 19:42, Guy Harris wrote:
> Gerhard Gappmeier wrot
Gerhard Gappmeier wrote:
> The problem is, that I want to output the field name, and not the type
> of a field.
> Is there a way to do that with /hf_register_info/?
Yes. The first element of a header_field_info structure is the name of
the field, and that's what's used in the display string wh
Hello,
I'm writing a dissector for a complex binary protocol that uses a lot of
nested structures, that are serialized on the wire.
All complex types are built on top of some basic simple types.
I'm generating the complex type parsers with a self written code generator
and only write the parsers f
