Wireshark · Wireshark-dev: Re: [Wireshark-dev] Frame Data Buffer Allocation

ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] Frame Data Buffer Allocation

From: Guy Harris <guy@xxxxxxxxxxxx>

Date: Mon, 5 Mar 2018 11:29:26 -0800

On Mar 5, 2018, at 2:16 AM, Paul Offord <Paul.Offord@xxxxxxxxxxxx> wrote:
 
> I’m not sure what I am supposed to do at that point.  Should my block handler just free the 2KB and then g_malloc a block of a suitable size?

No, you're supposed to do what every capture file reader does, and grow the buffer to the required size, using ws_buffer_assure_space().

Follow-Ups:
- Re: [Wireshark-dev] Frame Data Buffer Allocation
  - From: Paul Offord

References:
- [Wireshark-dev] Frame Data Buffer Allocation
  - From: Paul Offord

Prev by Date: Re: [Wireshark-dev] Submit code .... from Windows OS
Next by Date: Re: [Wireshark-dev] Frame Data Buffer Allocation
Previous by thread: [Wireshark-dev] Frame Data Buffer Allocation
Next by thread: Re: [Wireshark-dev] Frame Data Buffer Allocation
Index(es):
- Date
- Thread

© Wireshark Foundation · Privacy Policy

Facebook·Mastodon·Twitter·YouTube