https://bugs.kde.org/show_bug.cgi?id=492255
Marko Mäkelä <marko.mak...@iki.fi> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Ever confirmed|0 |1
Resolution|NOT A BUG |---
--- Comment #2 from Marko Mäkelä <marko.mak...@iki.fi> ---
Paul Floyd, it looks like you misread the report.
As the EXPECTED RESULT section explains, Invoking Valgrind would already result
in an instant failure on -fsanitize=address compiled code. I agree that that is
not a bug, but this report is about something else.
This report is about MemorySanitizer (clang -fsanitize=memory). Instead of
instantly failing, Valgrind would start to spend excessive CPU time on
processing an mmap() system call that is part of the MemorySanitizer
initialization.
I filed this bug on the request of the maintainer of
https://www.lysator.liu.se/~nisse/nettle/. The configure script in Nettle 3.10
attempts to invoke valgrind on a trivial program, and there is no way to
disable that check (other than by removing valgrind from $PATH). I need to
compile Nettle with -fsanitize=memory because it is a dependency of something
that needs to be tested with -fsanitize=memory:
https://jira.mariadb.org/browse/MDEV-20377
--
You are receiving this mail because:
You are watching all bug changes.
