qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Bulekov <alxndr@bu.edu>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>, Bandan Das <bsd@redhat.com>,
	Thomas Huth <thuth@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] fuzz: Add support for custom fuzzing library
Date: Tue, 1 Sep 2020 20:39:48 +0200	[thread overview]
Message-ID: <dde8a8f1-a4b0-11ec-6247-c35004863598@redhat.com> (raw)
In-Reply-To: <20200901181800.326382-1-alxndr@bu.edu>

On 01/09/20 20:18, Alexander Bulekov wrote:
> Maybe if I can get the oss-fuzz LIB_FUZZING_ENGINE
> (/usr/lib/libFuzzingEngine.a) into the --start-group, that could also
> solve the issue... I'll take another look at exactly what the oss-fuzz
> build container does.

Yeah, that might do it.  You can try adding it to the fork_fuzz dependency.

Paolo



  reply	other threads:[~2020-09-01 18:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 22:58 [Fwd] Issue 25164 in oss-fuzz: qemu: Fuzzing build failure Alexander Bulekov
2020-08-25  7:58 ` Paolo Bonzini
2020-08-26 13:55   ` Alexander Bulekov
2020-08-26 15:15     ` Paolo Bonzini
2020-08-28 18:33       ` Alexander Bulekov
2020-08-28 19:41         ` Paolo Bonzini
2020-09-01 18:18           ` [PATCH] fuzz: Add support for custom fuzzing library Alexander Bulekov
2020-09-01 18:39             ` Paolo Bonzini [this message]
2020-09-01 19:00             ` Paolo Bonzini
2020-09-02 12:27             ` no-reply
2020-09-02 12:31             ` no-reply
2020-09-02 12:33             ` no-reply

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=dde8a8f1-a4b0-11ec-6247-c35004863598@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alxndr@bu.edu \
    --cc=bsd@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@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).