On 18/09/18 01:07, Maynard, Chris wrote:
Thanks for the tips Richard, but after some additional testing and some 
head-scratching, I discovered the source of the problem was something in my 
profile, because if I switched to a pristine profile, then master ran fine.  
Through divide-and-conquer/trial-and-error, I discovered that it was due to 
enabling the transum dissector, although I can't figure out why enabling the 
transum dissector causes this, and then only for master.  Enabling it for 2.6.2 
seems fine.

Maybe someone could just confirm if they also experience this exception if they 
enable the transum dissector?  If confirmed, I will file a bug report.

Confirmed on the latest master. Enabling transum crashes wireshark.

The exception, for reference:

Unhandled exception ("proto.c:6497: failed assertion "(guint)hfid < gpa_hfinfo.len" 
(Unregistered hf!)", group=1, code=6)

Thanks.
- Chris

-----Original Message-----
From: Wireshark-dev [mailto:[email protected]] On Behalf Of 
Richard Sharpe
Sent: Monday, September 17, 2018 4:22 PM
To: Developer support list for Wireshark <[email protected]>
Subject: Re: [Wireshark-dev] Unhandled exception

<snip>











CONFIDENTIALITY NOTICE: This message is the property of International Game 
Technology PLC and/or its subsidiaries and may contain proprietary, 
confidential or trade secret information.  This message is intended solely for 
the use of the addressee.  If you are not the intended recipient and have 
received this message in error, please delete this message from your system. 
Any unauthorized reading, distribution, copying, or other use of this message 
or its attachments is strictly prohibited.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
              mailto:[email protected]?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
            mailto:[email protected]?subject=unsubscribe

Reply via email to