qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Bulekov <alxndr@bu.edu>
To: Yan Zhiqiang <yanz3q@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: About libfuzzer in qemu
Date: Sun, 7 Mar 2021 22:52:00 -0500	[thread overview]
Message-ID: <20210308035200.averk4yfddkqttyf@mozz.bu.edu> (raw)
In-Reply-To: <20210308034253.m6rjohwqcuynsaip@mozz.bu.edu>

On 210307 2242, Alexander Bulekov wrote:
> My basic workflow for that is:
> QEMU_FUZZ_TIMEOUT=0 QTEST_LOG=1 FUZZ_SERIALIZE_QTEST=1 \
> ./qemu-fuzz-target \
>        --fuzz-target=generic-fuzz-virtio-vga ./crash-... > /tmp/out
                                                           ^
                                        Oops that should be 2> or &>

> ./scripts/oss-fuzz/reorder_fuzzer_qtest_trace.py /tmp/out > /tmp/repro
> 
> # In /tmp/out find the line "Starting qemu with Arguments:" and copy the
> # args ( without -qtest /dev/null)
> less /tmp/out 
> 
> export QEMU_ARGS="-display none -machine accel=qtest, -m 512M -machine q35 -nodefaults -device virtio-vga"
> 
> # Reproduce the crash on a non-fuzz binary
> ./qemu-system-i386 $QEMU_ARGS -qtest stdio < /tmp/repro


      reply	other threads:[~2021-03-08  3:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAB7jVHGXcAdYg+z=Dgwb5LBhTxjWG_BALdwh+0CvUUucTzFehg@mail.gmail.com>
2021-03-04 15:23 ` About libfuzzer in qemu Alexander Bulekov
2021-03-05  7:51   ` Qiuhao Li
2021-03-05 14:48     ` Alexander Bulekov
     [not found]   ` <CAB7jVHECxxStzzV+5=7w_4QPwMxLRG5HE1Un97fCoxi72_MUBA@mail.gmail.com>
     [not found]     ` <20210306051010.rfg3ox2yo3hwmn2c@mozz.bu.edu>
     [not found]       ` <CAB7jVHHFc9FsnZmgGGwBLTON_8u2f8o5M6XJ1s9bZxShT+_ksQ@mail.gmail.com>
2021-03-08  3:42         ` Alexander Bulekov
2021-03-08  3:52           ` 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=20210308035200.averk4yfddkqttyf@mozz.bu.edu \
    --to=alxndr@bu.edu \
    --cc=qemu-devel@nongnu.org \
    --cc=yanz3q@gmail.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).