John Sullivan wrote:
> On Tuesday, October 12, 2010, 3:27:09 PM, Jeff Morriss wrote:
>> I think composite tvbuffs probably do work, but their use is hindered by
>> the fact that each tvb that you get (each time a frame is handed to your
>> dissector) is freed/reused after the packet is dissected.
On Tuesday, October 12, 2010, 3:27:09 PM, Jeff Morriss wrote:
> I think composite tvbuffs probably do work, but their use is hindered by
> the fact that each tvb that you get (each time a frame is handed to your
> dissector) is freed/reused after the packet is dissected. That is,
> Wireshark doe
Scott Mueller wrote:
> Hello Wireshark Dev List,
>
> I’ve been working with my own dissector for some time now and have run
> into a bit of a snag involving memory usage. I have messages that are
> split up on a size boundary, so I allocate enough space for the overall
> message (yes, I know th
f Of Scott Mueller
Sent: Monday, September 27, 2010 1:43 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] composite tvbuffs
Hi Stephen,
Section 2.7.2 is basically about doing the work that tcp_dissect_pdus
does, and that is certainly an option. Large messages composed in t
hen Fisher
Sent: Friday, September 24, 2010 10:17 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] composite tvbuffs
On Fri, Sep 24, 2010 at 05:33:25PM -0700, Scott Mueller wrote:
> Thank you for your response. I'm working with a multi-layered protocol
> that relies on
On Fri, Sep 24, 2010 at 05:33:25PM -0700, Scott Mueller wrote:
> Thank you for your response. I'm working with a multi-layered protocol
> that relies on TCP/IP, and in some cases the contiguous payload that I
> need to work with is spread out across several well-formed messages.
Have you looked
10 5:23 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] composite tvbuffs
On Fri, Sep 24, 2010 at 01:12:17PM -0700, Scott Mueller wrote:
> I have messages that are split up on a size boundary
What exactly do you mean? That within a captured packet in Wireshark,
eac
On Fri, Sep 24, 2010 at 01:12:17PM -0700, Scott Mueller wrote:
> I have messages that are split up on a size boundary
What exactly do you mean? That within a captured packet in Wireshark,
each message you need to dissect starts a certain byte positions or...?
> This is great, because I then pa
Hello Wireshark Dev List,
I've been working with my own dissector for some time now and have run
into a bit of a snag involving memory usage. I have messages that are
split up on a size boundary, so I allocate enough space for the overall
message (yes, I know this is a bit of a red flag) with s
