public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
	ClusterFuzz-External via monorail
	Evgeny Vereshchagin <>
Subject: Re: Issue 56085 in oss-fuzz: elfutils: Fuzzing build failure
Date: Fri, 17 Feb 2023 21:16:14 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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.


On Fri, Feb 17, 2023 at 10:04:40AM -0800, ClusterFuzz-External via monorail via Elfutils-devel wrote:
> Status: New
> Owner: ----
> CC:,,, 
> Labels: Proj-elfutils
> Type: Build-Failure
> New issue 56085 by ClusterFuzz-External: elfutils: Fuzzing build failure
> The last 3 builds for elfutils have been failing.
> Build log:
> Build type: fuzzing
> To reproduce locally, please see:
> This bug tracker is not being monitored by OSS-Fuzz team. If you have any questions, please create an issue at
> **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:
> Reply to this email to add a comment.

  reply	other threads:[~2023-02-17 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).