[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <545CB06B.8010302@samsung.com>
Date: Fri, 07 Nov 2014 14:43:39 +0300
From: Yury Gribov <y.gribov@...sung.com>
To: oss-security@...ts.openwall.com
Cc: binutils@...rceware.org, cherepan@...me.ru
Subject: Re: Re: Fuzzing objdump (PR 17512) and readelf (PR
17531)
On 11/07/2014 01:59 PM, Hanno Böck wrote:
> Am Fri, 07 Nov 2014 13:08:09 +0300
> schrieb Yury Gribov <y.gribov@...sung.com>:
>
>> This looks rather impressive. Have you considered automatically
>> detecting duplicates by e.g. analyzing stacktraces?
>
> american-fuzzy-lop kind of does that. It creates a hash among the code
> path and groups fuzzing samples by that. That's quite convenient.
[Cc-ing Binutils ML back again]
Yeah, I think there was even an article in one of recent PLDIs which
discussed different approaches to filtering duplicates arising in
compiler fuzz testing (they did various combinations of stacktraces,
Valgrind output, program coverage, etc.). I was just curious how well
this works for real world tasks like objdump crashes.
-Y
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
