Hi Pasqual,
you're right.
I've fixed it using wmem_alloc().
Thanks everyone
Antonello
Il giorno gio 27 mag 2021 alle ore 09:00 Pascal Quantin <
pas...@wireshark.org> ha scritto:
> Hi Antonello
>
> Le jeu. 27 mai 2021 à 08:54, Antonello Tartamo
> a écrit :
>
>> pt contains 16 bytes I have filled
Hi Antonello
Le jeu. 27 mai 2021 à 08:54, Antonello Tartamo
a écrit :
> pt contains 16 bytes I have filled up.
> I'm telling proto_tree_add_item to read these bytes from offset 0 with
> length 16.
> The field is properly shown (correct bytes) in the Packet Details tree but
> when I select it in
pt contains 16 bytes I have filled up.
I'm telling proto_tree_add_item to read these bytes from offset 0 with
length 16.
The field is properly shown (correct bytes) in the Packet Details tree but
when I select it in the Packet Bytes view the bytes selected are not the
same shown in the Packet Detai
You misunderstood. pt must contain the bytes you want to be inside the
subset. It seems, that you collect different bytes for this array as you
select for your hf_item selection which is then highlighted in the
packet-view
kind regard
Roland
Am Mi., 26. Mai 2021 um 14:39 Uhr schrieb Antonello Tar
Hello pt is an array (uint8_t pt[16];).
pt is an array generated after processing a part of the packet.
As I've created a new tvb the offset is 0 and the length is 16.
Hope I've answered your questions.
Il giorno mer 26 mag 2021 alle ore 14:32 Roland Knall ha
scritto:
> The data displayed in
The data displayed in the subitem is the one from pt, your data variable
which you used to create the new tvb. The hf_item seems to point to a
different data structure. How is pt being generated? Are you using the same
length and start offset as for the hf item?
regards
Roland
Am Mi., 26. Mai 202
Hello everyone,
I'm trying to add a custom item which is not strictly related to the packet
but it is coming from a processing of a part of the packet.
I've used the following instructions:
new_tvb = tvb_new_child_real_data(tvb, pt, (guint)16, 16);
add_new_data_sour
