From: Mark Wielaard <mark@klomp.org>
To: oss-fuzz@monorail-prod.appspotmail.com
Cc: elfutils-devel@sourceware.org,
ClusterFuzz-External via monorail
<monorail+v2.382749006@chromium.org>,
Evgeny Vereshchagin <evverx@gmail.com>
Subject: Re: Issue 56085 in oss-fuzz: elfutils: Fuzzing build failure
Date: Fri, 17 Feb 2023 21:16:14 +0100 [thread overview]
Message-ID: <20230217201614.GB5840@gnu.wildebeest.org> (raw)
In-Reply-To: <000000000000b6e8eb05f4e92520@google.com>
Hi Evgeny,
Sorry, another change that seems to break the fuzzer. You probably
don't have libstdc++-devel in your setup. If you cannot install that
you now have to explicitly configure with --disable-demangler.
I'll add the following note to the NEWS file:
diff --git a/NEWS b/NEWS
index 80faca39..72e1dd35 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,8 @@
Version 0.189
+configure: eu-nm, eu-addr2line and eu-stack can provide demangled symbols
+ when linked with libstdc++. Use --disable-demangler to disable.
+
libdwfl: dwfl_module_return_value_location now returns 0 (no return type)
for DIEs that point to a DW_TAG_unspecified_type.
Cheers,
Mark
On Fri, Feb 17, 2023 at 10:04:40AM -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 56085 by ClusterFuzz-External: elfutils: Fuzzing build failure
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56085
>
> The last 3 builds for elfutils have been failing.
> Build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-9be2ab33-042f-4f27-852a-bab7b60db7f0.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.**
>
> --
> 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.
next prev parent reply other threads:[~2023-02-17 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=cba38763e62f4aa6f0edc37959bb7ae1=oss-fuzz@monorail-prod.appspotmail.com>
2023-02-17 18:04 ` ClusterFuzz-External via monorail
2023-02-17 20:16 ` Mark Wielaard [this message]
2023-02-17 22:33 ` Evgeny Vereshchagin
2023-02-19 0:05 ` 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=20230217201614.GB5840@gnu.wildebeest.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).