Issue 56085 in oss-fuzz: elfutils: Fuzzing build failure

Issue 56085 in oss-fuzz: elfutils: Fuzzing build failure

[ClusterFuzz-External via monorail]

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

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.

Re: Issue 56085 in oss-fuzz: elfutils: Fuzzing build failure

[Mark Wielaard]

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.

Re: Issue 56085 in oss-fuzz: elfutils: Fuzzing build failure

[Evgeny Vereshchagin]

Hi Mark,

> You probably
> don't have libstdc++-devel in your setup.  If you cannot install that
> you now have to explicitly configure with --disable-demangler.

Thanks! I opened https://github.com/google/oss-fuzz/pull/9745 where I turned
the demangler off.

libstdc++-dev was indeed missing on "i386" but I think it's fine
because it doesn't affect the fuzz targets in any way. They only need
the static libraries
from libdw, libelf and so on.

Thanks,
Evgeny Vereshchagin

Issue 56085 in oss-fuzz: elfutils: Fuzzing build failure

[ClusterFuzz-External via monorail]

[-- Attachment #1: Type: text/plain, Size: 443 bytes --]

Updates:
	Status: Verified

Comment #1 on issue 56085 by ClusterFuzz-External: elfutils: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56085#c1

The latest build has succeeded, closing this issue.

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