zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Eduardo Bustamante <dualbus@gmail.com>, zsh-workers@zsh.org
Subject: Re: Zsh parser malloc corruption
Date: Mon, 8 May 2017 19:12:56 +0000	[thread overview]
Message-ID: <20170508191256.GA32024@fujitsu.shahaf.local2> (raw)
In-Reply-To: <20170508161024.3900768d@pwslap01u.europe.root.pri>

Peter Stephenson wrote on Mon, May 08, 2017 at 16:10:24 +0100:
> On Mon, 8 May 2017 09:20:38 -0500
> Eduardo Bustamante <dualbus@gmail.com> wrote:
> > On Mon, May 8, 2017 at 9:11 AM, Peter Stephenson
> > <p.stephenson@samsung.com> 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.

Agreed.  Also, thank you Eduardo for the reports!  Much appreciated.


  reply	other threads:[~2017-05-08 19:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170508135522epcas1p2c81789e7cafaa2c46e00eed1472af895@epcas1p2.samsung.com>
2017-05-08 13:53 ` Eduardo Bustamante
2017-05-08 14:11   ` Peter Stephenson
2017-05-08 14:16     ` Eduardo Bustamante
2017-05-08 14:20     ` Eduardo Bustamante
2017-05-08 15:10       ` Peter Stephenson
2017-05-08 19:12         ` Daniel Shahaf [this message]
2017-05-10  6:21   ` Bart Schaefer
2017-05-11 16:15     ` Peter Stephenson
2017-05-11 21:09       ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170508191256.GA32024@fujitsu.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=dualbus@gmail.com \
    --cc=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).