Wireshark-dev: Re: [Wireshark-dev] col_add_fence for Source/Dest columns?
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: "Abhik Sarkar" <sarkar.abhik@xxxxxxxxx>
Date: Thu, 17 Jul 2008 11:15:13 +0400
Hi David,

If you are trying to prevent a sub dissector from over-writing the
columns, you probably want to check the col_set_writable call as well.
See, packet-gsm_sms_ud (at around line 390) for an example.

HTH
Abhik.

On Wed, Jul 16, 2008 at 8:02 AM, David Underhill <dgu@xxxxxxxxxxxx> wrote:
> I am trying to prevent a call to call_dissector from overwriting the data in
> the source/dest fields in the main wireshark table.  However, even if I
> setup a fence on every value in the enum in column_info.h, they still get
> overwritten.  This is odd because setting fences on COL_PROTOCOL and
> COL_INFO protects the protocol and info fields as expected.
>
> Any ideas?
>
> ~ David