[Roland Knall <rknall@xxxxxxxxx>]

Please create a bug report and attach an example trace.

cheers

Roland

On Fri, Mar 2, 2018 at 7:30 PM, Paul Offord <Paul.Offord@xxxxxxxxxxxx> wrote:

I’ve written a new block dissector called blocktype-trb – see https://code.wireshark.org/review/#/c/26203/  It works OK but I have a strange problem.

 

I’ve added a profile for the new dissector that adds trb columns into the packet list.  With this profile active I load a pcapng file with trb blocks and get this:

 

 

If I then do anything to cause a rescan (in this case change to Default profile and then back to my customer profile), the columns are populated:

 

 

Any ideas what I have missed?

 

Thanks and 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
______________________________________________________________________

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe