Wireshark mailing list archives
Re: allocator->in_scope
From: Guy Harris <guy () alum mit edu>
Date: Sun, 25 Mar 2018 11:57:56 -0700
On Mar 25, 2018, at 11:35 AM, Paul Offord <Paul.Offord () advance7 com> wrote:
I have real dissector code that builds a protocol tree and so I guess this falls under libwireshark.
Yes.
However, I also have two block read functions that are registered like this: register_pcapng_block_type_handler((guint)BLOCK_TYPE_TDB, tdb_read_block, NULL); register_pcapng_block_type_handler((guint)BLOCK_TYPE_TRB, trb_read_block, NULL); Are my block read functions part of libwiretap?
Yes. ___________________________________________________________________________ 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:
- allocator->in_scope Paul Offord (Mar 25)
- Re: allocator->in_scope Paul Offord (Mar 25)
- Re: allocator->in_scope Evan Huus (Mar 25)
- Re: allocator->in_scope Paul Offord (Mar 25)
- Re: allocator->in_scope Guy Harris (Mar 25)
- Re: allocator->in_scope Paul Offord (Mar 25)
- Re: allocator->in_scope Guy Harris (Mar 25)
- Re: allocator->in_scope Paul Offord (Mar 25)