[Wireshark-dev] Handling malformed packet exceptions from within ASN.1 dissectors

2020-11-02 Thread Richard Sharpe
Hi folks, I am using some of the existing ASN.1 dissectors from within the ieee802.11 dissector, and in some cases the frame is malformed in the ASN.1 portion. However, since it is within an IE where I know the length of the element, I would like to regain control and add an Expert Info and then

Re: [Wireshark-dev] Handling malformed packet exceptions from within ASN.1 dissectors

2020-11-02 Thread Anders Broman via Wireshark-dev
: [Wireshark-dev] Handling malformed packet exceptions from within ASN.1 dissectors Hi folks, I am using some of the existing ASN.1 dissectors from within the ieee802.11 dissector, and in some cases the frame is malformed in the ASN.1 portion. However, since it is within an IE where I know the length of

Re: [Wireshark-dev] Handling malformed packet exceptions from within ASN.1 dissectors

2020-11-03 Thread Richard Sharpe
On Mon, Nov 2, 2020 at 11:57 PM Anders Broman via Wireshark-dev wrote: > > Hi, > I think a TRY CATCH block is the thing to use. Grep for CTACH and I think you > will find a bunch of examples. Yeah, I found them. But then I found that the ASN.1 dissectors already handle the situation and my probl