Hi Evgeny, On Wed, 2023-02-15 at 20:07 +0300, Evgeny Vereshchagin via Elfutils- devel wrote: > 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.
Thanks. That seems to have worked. > > 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! It helped to pinpoint the issue. I think it would be better if > it was possible to turn off --no-undefined > separately to make it easier to build elfutils on OSS-Fuzz (where I > can't pass `--enable-sanitize-*`) and avoid > build failures like that going forward. It was discussed in > https://sourceware.org/pipermail/elfutils-devel/2021q4/004418.html > but didn't go anywhere though. Why can't you simply use the configure support? We try to make it so that things just work to enable the different sanitizers. Also I think there is simply a bug in clang that it doesn't link properly with libasan/ubsan when -fsanitize=address/undefined is given. If you could add a configure check for that bug then we could add the no no-undefined trick independent of compiler used. Cheers, Mark
