Yes the composite TVB is displayed as single sequence but the composite is in fact several TVBs concatenated together,
so when I click on a field that was generated from the second concatenated TVB, it is displays in the byte pane as if it's the base of the sequence and not its proper offset.
For example:
Let's say I have 3 data chunks that create the composite: chunk1, chunk2, chunk3, each of size 0x0300.
So what I see is that the data from chunk2 or chunk3, though displayed correctly in the fields pane, is always zero based in the byte pane.
That is, instead of chunk2 highlighting bytes 0x0300 'til 0x0600, it again highlights 0x0000 'til 0x0300 (chunk1's area)
Oh, and I'm running Wireshark 1.8.3 32-bit compilation on windows 7, if it helps.
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Bill Meier
Sent: Monday, November 19, 2012 10:21 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] TVB Composite packet byte pane problem
On 11/19/2012 2:48 PM, Zadik, Maayan wrote:
> Hi,
>
> I'm using TVB composite to assemble some data chunks, using
> tvb_new_child_real_data.
>
> My problem is that every chunk is displayed in the byte pane as if
> it's at offset=0 instead of its actual location in the original TVB.
>
> Does anybody know how I can fix this?
>
>
I'm not sure I understand, especially with respect to the phrase "every chunk is displayed in the byte pane as if it's at offset=0".
A composite TVB is, in effect, a virtual TVB and will be displayed as a single sequence of bytes (numbered from 0 to ...) with no indication as to the underlying components from other TVBs.
Can you provide a bit more detail as to what you are trying to accomplish ?
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
