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.ca...@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, > 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 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.** >
