Wireshark-dev: Re: [Wireshark-dev] causes for losing COL_PROTOCOL or COL_INFO data
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Peter Wu <peter@xxxxxxxxxxxxx>
Date: Sat, 16 Sep 2017 13:38:31 +0100
Hi John,

Are your col_* functions guarded/affected by a check like if(tree) or do they depend on pinfo->fd.visited? Are the affected frames triggering reassembly or exceptions?

Kind regards,
Peter
https://lekensteyn.nl
(pardon my brevity, top-posting and formatting, sent from my phone)


On 15 September 2017 22:09:33 BST, John Dill <John.Dill@xxxxxxxxxxxxxxxxx> wrote:
>I'm setting the column fields and they appear to be set fine when I
>first open Wireshark, but when I apply a packet filter, I lose
>information from the fields even though it appears that I'm still
>calling the same col_* functions in the dissection.  Then when I remove
>the filter expression, and the COL_INFO I set is still missing.  Is
>there a usual cause for this behavior?  I can't seem to discover what's
>causing it.
>
>
>
>Thanks,
>
>John D.