On Sat, Oct 18, 2025 at 04:43:59AM +0200, Mark Wielaard wrote: > An RC1 tarball for 3.26.0 is now available at > https://sourceware.org/pub/valgrind/valgrind-3.26.0.RC1.tar.bz2 > (md5sum = b7798804b18476104073009043ecc96d) > (sha1sum = bc1bffd272b3a14b3ba9c1cc5a25a5e3975b9c8a) > https://sourceware.org/pub/valgrind/valgrind-3.26.0.RC1.tar.bz2.asc > > Please give it a try in configurations that are important for you and > report any problems you have, either on this mailing list, or > (preferably) via our bug tracker at > https://bugs.kde.org/enter_bug.cgi?product=valgrind > > The final 3.26.0 release is scheduled for Fri Oct 24.
The following are the test results on Fedora rawhide. i686: == 841 tests, 4 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/descr_belowsp (stderr) memcheck/tests/x86-linux/scalar (stderr) drd/tests/std_thread2 (stderr) none/tests/x86/lzcnt32 (stdout) none/tests/x86/lzcnt32 (stderr) x86_64: == 853 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/descr_belowsp (stderr) helgrind/tests/tc22_exit_w_lock (stderr) drd/tests/std_thread2 (stderr) aarch64: == 768 tests, 19 stderr failures, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures == gdbserver_tests/hgtls (stdoutB) memcheck/tests/arm64-linux/scalar (stderr) memcheck/tests/descr_belowsp (stderr) memcheck/tests/dw4 (stderr) memcheck/tests/fwrite (stderr) memcheck/tests/linux/sys-copy_file_range (stderr) memcheck/tests/linux/sys-preadv_pwritev (stderr) memcheck/tests/sendmsg (stderr) memcheck/tests/varinfo2 (stderr) memcheck/tests/varinfo4 (stderr) memcheck/tests/varinfo5 (stderr) memcheck/tests/varinfo6 (stderr) memcheck/tests/varinforestrict (stderr) memcheck/tests/writev1 (stderr) helgrind/tests/hg05_race2 (stderr) helgrind/tests/tc20_verifywrap (stderr) drd/tests/tls_threads (stderr) none/tests/track_bad (stderr) none/tests/track_new (stderr) none/tests/use_after_close (stderr) ppc64le: == 760 tests, 12 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/descr_belowsp (stderr) memcheck/tests/fwrite (stderr) memcheck/tests/linux/sys-copy_file_range (stderr) memcheck/tests/linux/sys-preadv_pwritev (stderr) memcheck/tests/sendmsg (stderr) memcheck/tests/writev1 (stderr) helgrind/tests/getaddrinfo (stderr) none/tests/fdleak_cmsg_xml (stderr) none/tests/socket_close_xml (stderr) none/tests/track_bad (stderr) none/tests/track_new (stderr) none/tests/use_after_close (stderr) s390x: == 892 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 4 post failures == memcheck/tests/descr_belowsp (stderr) helgrind/tests/tc22_exit_w_lock (stderr) drd/tests/bar_bad_xml (stderr) none/tests/s390x/bfp-emit (post) none/tests/s390x/bfp-XxC (post) none/tests/s390x/dfp-XiC (post) none/tests/s390x/dfp-XxC (post) The last 4 look like I messed up the install: valgrind: failed to start tool 'none' for platform 's390x-linux': No such file or directory _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
