https://bugs.kde.org/show_bug.cgi?id=496370
--- Comment #3 from Paul Floyd <pjfl...@wanadoo.fr> --- It looks like this is compiler related. Back on S11.3 with an old GCC (4.8.2) I get == 860 tests, 18 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/amd64-solaris/context_fpu (stderr) memcheck/tests/solaris/lsframe2 (stderr) memcheck/tests/vcpu_fnfns (stdout) helgrind/tests/bar_bad (stderr) helgrind/tests/bar_trivial (stderr) helgrind/tests/bug322621 (stderr) helgrind/tests/free_is_write (stderr) helgrind/tests/pth_barrier1 (stderr) helgrind/tests/pth_barrier2 (stderr) helgrind/tests/pth_barrier3 (stderr) helgrind/tests/pth_mempcpy_false_races (stderr) helgrind/tests/tc21_pthonce (stderr) drd/tests/pth_cond_destroy_busy (stderr) drd/tests/std_mutex (stderr) none/tests/fdleak_dup2 (stderr) none/tests/fdleak_dup2_xml (stderr) none/tests/fdleak_pipe_xml (stderr) none/tests/fdleak_socketpair_xml (stderr) none/tests/file_dclose (stderr) and specifically memcheck/tests/signal2 is OK GCC 4.8.2 is too old to build Valgrind - there are some opcodes in asm that it doesn't know and it can't compile any C++ from C++17 onwards (and I'm not going to bother adding any configure checks for them). So I've been using a more recent GCC (12.0.1 20220425). That doesn't have build issues but signals are broken. Illumos is also using a relatively recent GCC (gcc (OpenIndiana 13.3.0-oi-0) 13.3.0). Valgrind built with the old GCC is OK with testcases built with GCC 12, so it's the build of Valgrind that matters. This looks like a big rabbit hole. -- You are receiving this mail because: You are watching all bug changes.
