From: Mark Wielaard <mark@klomp.org>
To: oss-fuzz@monorail-prod.appspotmail.com, elfutils-devel@sourceware.org
Cc: ClusterFuzz-External via monorail
<monorail+v2.382749006@chromium.org>,
Evgeny Vereshchagin <evverx@gmail.com>
Subject: Re: Issue 55999 in oss-fuzz: elfutils: Fuzzing build failure
Date: Wed, 15 Feb 2023 13:32:40 +0100 [thread overview]
Message-ID: <4398d0786626e419e5d0f92bf7d5e366634cd5d7.camel@klomp.org> (raw)
In-Reply-To: <0000000000000c7ee805f4bbd6fa@google.com>
Hi Evgeny,
Could you take a look at this. I think the problem is that the
clusterfuzz setup doesn't use configure --enable-sanitize-address
Note that we also recently got support for --enable-sanitize-memory but
that needs a bit of setup and only works with the clang compiler. See
https://inbox.sourceware.org/elfutils-devel/6e576e707fa3da14f4e9045cbf53ba887823a543.camel@linux.ibm.com/T/
Thanks,
Mark
On Wed, 2023-02-15 at 04:01 -0800, ClusterFuzz-External via monorail
via Elfutils-devel wrote:
> Status: New
> Owner: ----
> CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com, izzeem@google.com
> Labels: Proj-elfutils
> Type: Build-Failure
>
> New issue 55999 by ClusterFuzz-External: elfutils: Fuzzing build failure
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=55999
>
> The last 3 builds for elfutils have been failing.
> Build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-843b41d5-2949-48cb-9dbf-f05d5f435626.txt
> Build type: fuzzing
>
> To reproduce locally, please see: https://google.github.io/oss-fuzz/advanced-topics/reproducing#reproducing-build-failures
>
> This bug tracker is not being monitored by OSS-Fuzz team. If you have any questions, please create an issue at https://github.com/google/oss-fuzz/issues/new.
>
> **This bug will be automatically closed within a day once it is fixed.**
>
next prev parent reply other threads:[~2023-02-15 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=ce7b5f861c1a0d42714a49e3059f172a=oss-fuzz@monorail-prod.appspotmail.com>
2023-02-15 12:01 ` ClusterFuzz-External via monorail
2023-02-15 12:32 ` Mark Wielaard [this message]
2023-02-15 17:07 ` Evgeny Vereshchagin
2023-02-16 13:23 ` Mark Wielaard
2023-02-16 15:27 ` Evgeny Vereshchagin
2023-02-16 6:01 ` ClusterFuzz-External via monorail
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=4398d0786626e419e5d0f92bf7d5e366634cd5d7.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=evverx@gmail.com \
--cc=monorail+v2.382749006@chromium.org \
--cc=oss-fuzz@monorail-prod.appspotmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).