Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Zsh parser malloc corruption
- X-seq: zsh-workers 41071
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: Eduardo Bustamante <dualbus@xxxxxxxxx>, zsh-workers@xxxxxxx
- Subject: Re: Zsh parser malloc corruption
- Date: Mon, 08 May 2017 16:10:24 +0100
- Cms-type: 201P
- In-reply-to: <CAOSMAuvD0jOEnN=APg__gEYwe47k02-OCi=U90CfJLDx3G09aA@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- Organization: Samsung Cambridge Solution Centre
- References: <CGME20170508135522epcas1p2c81789e7cafaa2c46e00eed1472af895@epcas1p2.samsung.com> <CAOSMAusOHHM-4Y8w24wSwX6i5_YP2Q1nXD2cc6+jibXR=PNhKQ@mail.gmail.com> <20170508151114.746b72fa@pwslap01u.europe.root.pri> <CAOSMAuvD0jOEnN=APg__gEYwe47k02-OCi=U90CfJLDx3G09aA@mail.gmail.com>
On Mon, 8 May 2017 09:20:38 -0500
Eduardo Bustamante <dualbus@xxxxxxxxx> wrote:
> On Mon, May 8, 2017 at 9:11 AM, Peter Stephenson
> <p.stephenson@xxxxxxxxxxx> wrote:
> > I think it would probably help if you attach the files causing these
> > problems.
>
> By the way, I obtained all of these crashing inputs by running `Zsh
> -n' under the AFL fuzzer. I'm trying to go through the crashes I got
> and sort / classify. I don't know if you'd prefer for me to just
> upload the crashes in a compressed tarball somewhere and send you the
> link.
Separate reports are fine as they're probably typically different
issues.
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author