Wireshark mailing list archives
Re: Problem with val_to_str inside BASE_CUSTOM callback function
From: Guy Harris <guy () alum mit edu>
Date: Fri, 21 Oct 2016 13:17:09 -0700
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. ___________________________________________________________________________ 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
Current thread:
- Problem with val_to_str inside BASE_CUSTOM callback function Thomas Wiens (Oct 21)
- Re: Problem with val_to_str inside BASE_CUSTOM callback function Guy Harris (Oct 21)
- Re: Problem with val_to_str inside BASE_CUSTOM callback function Jaap Keuter (Oct 21)
- Re: Problem with val_to_str inside BASE_CUSTOM callback function Guy Harris (Oct 21)
- Re: Problem with val_to_str inside BASE_CUSTOM callback function Thomas Wiens (Oct 21)
- Re: Problem with val_to_str inside BASE_CUSTOM callback function Michael Mann (Oct 21)
- Re: Problem with val_to_str inside BASE_CUSTOM callback function Thomas Wiens (Oct 21)
- Re: Problem with val_to_str inside BASE_CUSTOM callback function Jaap Keuter (Oct 21)
- Re: Problem with val_to_str inside BASE_CUSTOM callback function Guy Harris (Oct 21)