Wireshark-dev: [Wireshark-dev] New pcap-ng block requires a rescan
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Paul Offord <Paul.Offord@xxxxxxxxxxxx>
Date: Wed, 4 Apr 2018 10:20:34 +0000

Hi,

 

I’ve reached a milestone with the TRB support; all basic Wireshark functionality is complete.  There is a remaining problem.  On opening a file, the blocks are decoded (see the protocol tree in the following screenshot) but the values are not rendered in the Packet List columns.

 

 

If I force a rescan (typically by changing to another profile and then back to the original profile), the column values are rendered.

 

 

I don’t think this is a problem with the TRB dissector.  I have tried figuring out what might be causing this problem, but I must admit I am struggling to understand how the column values are rendered.

 

Can someone give me a steer?  What areas should I be looking at?  How should I debug this problem?

 

Any help would be much appreciated.

 

Best regards…Paul

 


______________________________________________________________________

This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.

Any views or opinions expressed are solely those of the author and do not necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________