From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============3249414783389921007=="
MIME-Version: 1.0
From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: Fuzzing elfutils
Date: Tue, 23 Dec 2014 12:42:32 +0100
Message-ID: <20141223114232.GE8656@blokker.redhat.com>
In-Reply-To: 549747A8.3020804@mccme.ru

--===============3249414783389921007==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 22, 2014 at 01:20:24AM +0300, Alexander Cherepanov wrote:
> But it would be nice to have an idea which commits fix which crashes. Your
> first commit (d0070a9) included Reported-by: -- thanks! But it was the on=
ly
> such commit, then it was not clear whether you fix further crashes from t=
he
> same bunch or fix completely different crashes.

Sorry about that. Once I started to look seriously into the fuzzer crashers
I realized there were some fundemental issue that needed fixed. So I took
your and Hano and my own crashers and just put them into a big directory
running under valgrind looking for common patterns to fix.

> I guess I can formulate two wishes now:
> - to include Reported-by: tag in your commits (to make it possible to tra=
ck
> progress and as a credit);
> - to let me know when it's reasonable to start next round of fuzzing.

I'll do that. mjw/pending contains 2 patches that should fix your
most recent reported crashers. It is reasonable to start the next round
based on those now.

Thanks,

Mark

--===============3249414783389921007==--