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.d...@greenfieldeng.com> 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. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
