From: Fabiano Rosas <farosas@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Alexander Bulekov <alxndr@bu.edu>, Bandan Das <bsd@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Darren Kenny <darren.kenny@oracle.com>,
Qiuhao Li <Qiuhao.Li@outlook.com>
Subject: Re: [PATCH] docs/devel/testing/fuzzing: Note that you can get qtest to read from a file
Date: Tue, 28 Oct 2025 16:53:07 -0300 [thread overview]
Message-ID: <871pmmerbw.fsf@suse.de> (raw)
In-Reply-To: <20251028165236.3327658-1-peter.maydell@linaro.org>
Peter Maydell <peter.maydell@linaro.org> writes:
> It is possible to get qtest to read fuzzer reproducers from a file
> rather than directly from stdio; this is useful when you want to run
> QEMU under gdb to debug the failure. Document how to do this, which
> was previously only written down in the commit message for
> 5b18a6bf44b9 ("chardev: Allow setting file chardev input file on the
> command line").
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> I got bored of looking up the commit message in the git log
> every time :-)
> ---
> docs/devel/testing/fuzzing.rst | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/docs/devel/testing/fuzzing.rst b/docs/devel/testing/fuzzing.rst
> index c3ac084311b..c43f815f320 100644
> --- a/docs/devel/testing/fuzzing.rst
> +++ b/docs/devel/testing/fuzzing.rst
> @@ -263,6 +263,15 @@ generic-fuzz target.
>
> - Report the bug and send a patch with the C reproducer upstream
>
> +QEMU can also read the reproducer directly from a file rather than
> +from standard input::
> +
> + $QEMU_PATH $QEMU_ARGS -qtest chardev:repro \
> + -chardev file,id=repro,path=/dev/null,input-path=/tmp/reproducer
> +
> +This is useful if you want to run QEMU under a debugger to investigate
> +the failure.
> +
> Implementation Details / Fuzzer Lifecycle
> -----------------------------------------
Reviewed-by: Fabiano Rosas <farosas@suse.de>
next prev parent reply other threads:[~2025-10-28 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 16:52 [PATCH] docs/devel/testing/fuzzing: Note that you can get qtest to read from a file Peter Maydell
2025-10-28 19:53 ` Fabiano Rosas [this message]
2025-10-29 8:03 ` Manos Pitsidianakis
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=871pmmerbw.fsf@suse.de \
--to=farosas@suse.de \
--cc=Qiuhao.Li@outlook.com \
--cc=alxndr@bu.edu \
--cc=bsd@redhat.com \
--cc=darren.kenny@oracle.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.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 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).