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

2020-11-02 Thread Anders Broman via Wireshark-dev
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. Regards Anders -Original Message- From: Wireshark-dev On Behalf Of Richard Sharpe Sent: den 3 november 2020 00:26 To: Developer support list for Wireshark Subject: [Wireshar

[Wireshark-dev] Tweak bug template to get _all_ version info

2020-11-02 Thread Jaap Keuter
Hi, Again it’s seems difficult to get people to add _all_ version informalities when filing a bug report. Only the version string is copied then. We’ve introduced a “Copy to clipboard’ button on the About Wireshark dialog for this. Can the template be adjusted to direct users to use that button

[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] Building Wireshark 3.4.0 documentation on Windows

2020-11-02 Thread Gerald Combs
On 11/2/20 8:51 AM, Maynard, Chris via Wireshark-dev wrote: >> From: Wireshark-dev On Behalf Of >> Graham Bloice >> Sent: Monday, November 2, 2020 11:04 AM >> To: Developer support list for Wireshark >> Subject: Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on >> Windows >> >> FWIW

Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on Windows

2020-11-02 Thread Maynard, Chris via Wireshark-dev
> -Original Message- > From: Wireshark-dev On Behalf Of > John Dill > Sent: Monday, November 2, 2020 11:34 AM > To: wireshark-dev@wireshark.org > Subject: Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on > Windows > > I build on Windows primarily and I've had recent issues wit

Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on Windows

2020-11-02 Thread Graham Bloice
On Mon, 2 Nov 2020 at 16:34, John Dill wrote: > > >Message: 2 > >Date: Mon, 2 Nov 2020 16:04:21 + > >From: Graham Bloice > >To: Developer support list for Wireshark > >Subject: Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on > >Windows > >Message-ID: > > vavvun

Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on Windows

2020-11-02 Thread Maynard, Chris via Wireshark-dev
> From: Wireshark-dev On Behalf Of Graham > Bloice > Sent: Monday, November 2, 2020 11:04 AM > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on Windows > > FWIW, Strawberry Perl has failed to update for me with chocolatey the last

Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on Windows

2020-11-02 Thread John Dill
>Message: 2 >Date: Mon, 2 Nov 2020 16:04:21 + >From: Graham Bloice >To: Developer support list for Wireshark >Subject: Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on >Windows >Message-ID: > >Content-Type: text/plain; charset="utf-8" > >On Mon, 2 Nov 2020 at 15:

Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on Windows

2020-11-02 Thread Graham Bloice
On Mon, 2 Nov 2020 at 15:06, Maynard, Chris via Wireshark-dev < wireshark-dev@wireshark.org> wrote: > > -Original Message- > > From: Wireshark-dev On Behalf Of > > Gerald Combs > > Sent: Sunday, November 1, 2020 8:36 PM > > To: Developer support list for Wireshark ; > > Graham Bloice > >

Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on Windows

2020-11-02 Thread Maynard, Chris via Wireshark-dev
> -Original Message- > From: Wireshark-dev On Behalf Of > Gerald Combs > Sent: Sunday, November 1, 2020 8:36 PM > To: Developer support list for Wireshark ; > Graham Bloice > Subject: Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on > Windows > > On 11/1/20 2:29 PM, Graham Bl