https://bugs.kde.org/show_bug.cgi?id=523626
--- Comment #4 from [email protected] --- Trying to use compiler sanitizers to find problems in memcheck. I've found that it is not possible to use clang's asan with memcheck, because memcheck doesn't depend on libc, while asan needs it for its output. BUT it's possible to use UBsan: UBSan doesn't report using libc output functions. Instead sends SIGILL if it finds an UB. Which, alas, kind of conflicts with Valgrind's default use of SIGILL (see README_DEVELOPERS). But it kind of works - it gives some output. It's even possible to instrument a single CU this way - by extracting respective clang invocation from the build log and replaying that with "-fsanitize=undefined -fsanitize-trap=undefined -fno-omit-frame-pointer" added to the clang's command line. After this, `make` in the src root relinks the project. With this, memcheck gives some additional output. That output doesn't seem related to this bug though. -- You are receiving this mail because: You are watching all bug changes.
