Re: Problem with val_to_str inside BASE_CUSTOM callback function

[Thomas Wiens <th.wiens () gmx de>]

On 21.10.2016 22:17, Guy Harris wrote:
> On Oct 21, 2016, at 1:08 PM, Jaap Keuter <jaap.keuter () xs4all nl> wrote:
>
> > For my understanding, would this be covered by using
> > val_to_str_wmem(wmem_file_scope(), val, vs, fmt);
>
> Yes, but the strings will remain allocated until the capture file is closed, even if that's not necessary.

I think that I will use val_to_str_const instead, because I'm using more
than one val_to_str inside my callback function.

I already have problems with high memory usage, because in the protocol
I'm working on, I have to reassemble a possible huge number of packets
before dissecting them. Maybe I have to ask some of you experts in a
separate thread, of how to deal with this. Maybe there are also other
protocols which have the same issues.

It seems that no other dissector is using val_to_str inside the
callback. But I think that problem would occur at least with a fuzz test.

-- 
Thomas

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