On Thu, Sep 14, 2023 at 12:52 PM John Dill <
John.Dill@xxxxxxxxxxxxxxxxx> wrote:
>Message: 2
>Date: Tue, 12 Sep 2023 10:24:19 -0400
>From: John Thacker <johnthacker@xxxxxxxxx>
>To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
>Subject: Re: [Wireshark-dev] question on validation of a dissected
> string from a BASE_CUSTOM hf item
>Message-ID:
> <CAP_QLgpwRLiCnaPBvgEbiHQWGFC9KZOjNmacjoLtHybUZEybiA@xxxxxxxxxxxxxx>
>Content-Type: text/plain; charset="utf-8"
>
>You may have noticed "proto_tree_add_item_ret_display_string()" and perhaps
>found that it doesn't do what you want; it produces the display string for
>a default display representation and doesn't use your custom function.
>(Perhaps it should?)
Hi John,
I did notice that proto_item_add_item_ret_display_string and friends, but the intent doesn't appear to be
what I'm envisioning, since the list of FT types doesn't include any of the FT integer types, e.g. from proto.c (I'm still 3.6)
REPORT_DISSECTOR_BUG("field %s is not of type FT_STRING, FT_STRINGZ, FT_UINT_STRING,
FT_STRINGZPAD, FT_STRINGZTRUNC, FT_BYTES, or FT_UINT_BYTES",
It's still that way on the current master, but I think there's a solid use case for adding to that routine the ability to add an item and get what the standard representation would be. It's just not implemented yet.
John