From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Alexander Bulekov <alxndr@bu.edu>, qemu-devel@nongnu.org
Cc: bsd@redhat.com, stefanha@redhat.com
Subject: Re: [PATCH 2/4] docs/fuzz: describe building fuzzers with enable-sanitizers
Date: Tue, 7 Jul 2020 06:31:34 +0200 [thread overview]
Message-ID: <f2ac71c8-6f69-6e17-2a2a-e438c8f92bf0@redhat.com> (raw)
In-Reply-To: <20200706195534.14962-3-alxndr@bu.edu>
On 7/6/20 9:55 PM, Alexander Bulekov wrote:
> Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> docs/devel/fuzzing.txt | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/docs/devel/fuzzing.txt b/docs/devel/fuzzing.txt
> index 324d2cd92b..382ade974e 100644
> --- a/docs/devel/fuzzing.txt
> +++ b/docs/devel/fuzzing.txt
> @@ -23,9 +23,12 @@ AddressSanitizer mmaps ~20TB of memory, as part of its detection. This results
> in a large page-map, and a much slower fork().
>
> To build the fuzzers, install a recent version of clang:
> -Configure with (substitute the clang binaries with the version you installed):
> +Configure with (substitute the clang binaries with the version you installed).
> +Here, enable-sanitizers, is optional but it allows us to reliably detect bugs
> +such as out-of-bounds accesses, use-after-frees, double-frees etc.
>
> - CC=clang-8 CXX=clang++-8 /path/to/configure --enable-fuzzing
> + CC=clang-8 CXX=clang++-8 /path/to/configure --enable-fuzzing \
> + --enable-sanitizers
>
> Fuzz targets are built similarly to system/softmmu:
>
>
next prev parent reply other threads:[~2020-07-07 4:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 19:55 [PATCH 0/4] fuzz: misc patches Alexander Bulekov
2020-07-06 19:55 ` [PATCH 1/4] fuzz: build without AddressSanitizer, by default Alexander Bulekov
2020-07-07 4:30 ` Philippe Mathieu-Daudé
2020-07-20 16:49 ` Thomas Huth
2020-07-06 19:55 ` [PATCH 2/4] docs/fuzz: describe building fuzzers with enable-sanitizers Alexander Bulekov
2020-07-07 4:31 ` Philippe Mathieu-Daudé [this message]
2020-07-21 5:26 ` Thomas Huth
2020-07-06 19:55 ` [PATCH 3/4] docs/fuzz: add information about useful libFuzzer flags Alexander Bulekov
2020-07-06 19:55 ` [PATCH 4/4] docs/fuzz: add instructions for generating a coverage report Alexander Bulekov
2020-07-07 4:41 ` Alexander Bulekov
2020-07-21 5:31 ` Thomas Huth
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=f2ac71c8-6f69-6e17-2a2a-e438c8f92bf0@redhat.com \
--to=philmd@redhat.com \
--cc=alxndr@bu.edu \
--cc=bsd@redhat.com \
--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 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).