From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>, "Oleinik, Alexander" <alxndr@bu.edu>
Subject: Re: Issue 25514 in oss-fuzz: qemu: Coverage build failure
Date: Mon, 21 Sep 2020 14:10:56 +0200 [thread overview]
Message-ID: <995b1aa7-8efc-57d2-a85e-5520fab0755b@redhat.com> (raw)
In-Reply-To: <0000000000003aa8d805afd00f24@google.com>
On 21/09/20 12:10, ClusterFuzz-External via monorail wrote:
>
> Comment #2 on issue 25514 by ClusterFuzz-External: qemu: Coverage build
> failure
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25514#c2
>
> Friendly reminder that the the build is still failing.
> Please try to fix this failure to ensure that fuzzing remains productive.
> Latest build log:
> https://oss-fuzz-build-logs.storage.googleapis.com/log-632125f2-e66b-4480-9504-c1097198069a.txt
>
> --
> You received this message because:
> 1. You were specifically CC'd on the issue
>
> You may adjust your notification preferences at:
> https://bugs.chromium.org/hosting/settings
>
> Reply to this email to add a comment.
It's now failing with:
Step #3: /usr/bin/ld: section .interp loaded at
[00000000000002a8,00000000000002c3] overlaps section .data.fuzz_ordered
loaded at [0000000000000000,000000000016ebff]
Do you know what's going on? Also, should we make
scripts/oss-fuzz/build.sh use "make V=1"?
Paolo
next parent reply other threads:[~2020-09-21 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=0a88cf92d34dc9db91727cc9bd0dc58b=d9ca53ad17e3d19752f355e6c3ba1ecc=oss-fuzz@monorail-prod.appspotmail.com>
[not found] ` <0000000000003aa8d805afd00f24@google.com>
2020-09-21 12:10 ` Paolo Bonzini [this message]
2020-09-21 13:38 ` Issue 25514 in oss-fuzz: qemu: Coverage build failure Alexander Bulekov
2020-09-21 14:08 ` Paolo Bonzini
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=995b1aa7-8efc-57d2-a85e-5520fab0755b@redhat.com \
--to=pbonzini@redhat.com \
--cc=alxndr@bu.edu \
--cc=qemu-devel@nongnu.org \
/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).