From: Alexander Bulekov <alxndr@bu.edu>
To: qemu-devel@nongnu.org
Cc: darren.kenny@oracle.com, bsd@redhat.com, f4bug@amsat.org,
stefanha@redhat.com
Subject: Re: [PATCH 0/2] fuzz: add a script to help build reproducers
Date: Sat, 13 Mar 2021 23:28:11 -0500 [thread overview]
Message-ID: <20210314042811.asdlpix6tzoro3nw@mozz.bu.edu> (raw)
In-Reply-To: <20210314042358.682136-1-alxndr@bu.edu>
Here are examples of code generated by the script:
https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg06027.html
https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg06028.html
https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg06029.html
On 210313 2323, Alexander Bulekov wrote:
> Hello,
> This series adds a script that can be handy for reporting fuzzer bugs
> and creating regression-tests, based on crash reproducers.
>
> Patch 1 adds a script that can help create bash and C reproducers for
> crashes.
> Patch 2 documents the process of building reproducers.
>
>
> Alexander Bulekov (2):
> fuzz: add a script to build reproducers
> fuzz: add instructions for building reproducers
>
> docs/devel/fuzzing.rst | 45 ++++++++
> scripts/oss-fuzz/output_reproducer.py | 160 ++++++++++++++++++++++++++
> 2 files changed, 205 insertions(+)
> create mode 100755 scripts/oss-fuzz/output_reproducer.py
>
> --
> 2.28.0
>
prev parent reply other threads:[~2021-03-14 4:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 4:23 [PATCH 0/2] fuzz: add a script to help build reproducers Alexander Bulekov
2021-03-14 4:23 ` [PATCH 1/2] fuzz: add a script to " Alexander Bulekov
2021-03-15 11:41 ` Darren Kenny
2021-03-14 4:23 ` [PATCH 2/2] fuzz: add instructions for building reproducers Alexander Bulekov
2021-03-15 11:42 ` Darren Kenny
2021-03-14 4:28 ` Alexander Bulekov [this message]
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=20210314042811.asdlpix6tzoro3nw@mozz.bu.edu \
--to=alxndr@bu.edu \
--cc=bsd@redhat.com \
--cc=darren.kenny@oracle.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.