Wireshark · Wireshark-dev: Re: [Wireshark-dev] Problem with val_to_str inside BASE_CUSTOM callback function

Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Problem with val_to_str inside BASE_CUSTOM callback function

From: Guy Harris <guy@xxxxxxxxxxxx>

Date: Fri, 21 Oct 2016 13:17:09 -0700

On Oct 21, 2016, at 1:08 PM, Jaap Keuter <jaap.keuter@xxxxxxxxx> 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.

Follow-Ups:
- Re: [Wireshark-dev] Problem with val_to_str inside BASE_CUSTOM callback function
  - From: Thomas Wiens

References:
- [Wireshark-dev] Problem with val_to_str inside BASE_CUSTOM callback function
  - From: Thomas Wiens
- Re: [Wireshark-dev] Problem with val_to_str inside BASE_CUSTOM callback function
  - From: Guy Harris
- Re: [Wireshark-dev] Problem with val_to_str inside BASE_CUSTOM callback function
  - From: Jaap Keuter

Prev by Date: Re: [Wireshark-dev] Problem with val_to_str inside BASE_CUSTOM callback function
Next by Date: [Wireshark-dev] Intro and lua question
Previous by thread: Re: [Wireshark-dev] Problem with val_to_str inside BASE_CUSTOM callback function
Next by thread: Re: [Wireshark-dev] Problem with val_to_str inside BASE_CUSTOM callback function
Index(es):
- Date
- Thread

© Wireshark Foundation · Privacy Policy

Facebook·Mastodon·Twitter·YouTube