Updates:
Status: Verified
Comment #1 on issue 55999 by ClusterFuzz-External: elfutils: Fuzzing build
failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=55999#c1
The latest build has succeeded, closing this issue.
--
You received this message because:
1. You were specifical
https://sourceware.org/bugzilla/show_bug.cgi?id=30085
Mark Wielaard changed:
What|Removed |Added
CC||mark at klomp dot org
--- Comment #1
Hi Mark,
I fixed the build failure in
https://github.com/google/oss-fuzz/pull/9718. Once it's merged
and reaches ClusterFuzz OSS-Fuzz should close the issue.
> Note that we also recently got support for --enable-sanitize-memory but
> that needs a bit of setup and only works with the clang compile
There have been a couple of cases where demangler support has been
accidentially been disabled because libstdc++ wasn't there/installed
during build. Make it an error if --disable-demangler isn't explicitly
given.
Signed-off-by: Mark Wielaard
---
ChangeLog| 5 +
configure.ac | 3 ++-
2 f
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.s
Status: New
Owner:
CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com,
izz...@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
