Hi, On Wed, Oct 21, 2026 at 06:29:41PM +0200, Mark Wielaard wrote: > An RC1 tarball for 3.28.0 is now available at > https://sourceware.org/pub/valgrind/valgrind-3.28.0.RC1.tar.bz2 > (md5sum = acf7e55f91e2a84c4e2cf3488cf82ff4) > (sha1sum = 3219492de4656a2df5865571baefbda0f8b16d85) > https://sourceware.org/pub/valgrind/valgrind-3.28.0.RC1.tar.bz2.asc > Public keys can be found at https://www.klomp.org/mark/gnupg-pub.txt > > 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 > > Unless showstopper bugs are found (and cannot be easily fixed) > the final 3.28.0 release is scheduled for this Fri Oct 23.
Some results from the Fedora (rawhide) builds. - i686 https://kojipkgs.fedoraproject.org/packages/valgrind/3.28.0/0.1.RC1.fc46/data/logs/i686/build.log == 865 tests, 4 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/linux/madv_guard (stdout) memcheck/tests/x86-linux/scalar (stderr) drd/tests/pth_detached3 (stderr) none/tests/fdleak_cat (stderr) none/tests/fdleak_cmsg_supp (stderr) - x86_64 https://kojipkgs.fedoraproject.org/packages/valgrind/3.28.0/0.1.RC1.fc46/data/logs/x86_64/build.log == 877 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures == gdbserver_tests/hgtls (stdoutB) drd/tests/pth_detached3 (stderr) drd/tests/tls_threads (stderr) none/tests/fdleak_cat (stderr) - aarch64 https://kojipkgs.fedoraproject.org/packages/valgrind/3.28.0/0.1.RC1.fc46/data/logs/aarch64/build.log == 790 tests, 22 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/dw4 (stderr) memcheck/tests/err_disable4 (stderr) memcheck/tests/thread_alloca (stderr) memcheck/tests/varinfo2 (stderr) memcheck/tests/varinfo4 (stderr) memcheck/tests/varinfo5 (stderr) memcheck/tests/varinfo6 (stderr) memcheck/tests/varinforestrict (stderr) helgrind/tests/annotate_smart_pointer (stderr) helgrind/tests/hg05_race2 (stderr) helgrind/tests/pth_barrier3 (stderr) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tls_threads2 (stderr) drd/tests/annotate_smart_pointer (stderr) drd/tests/concurrent_close (stderr) drd/tests/pth_barrier3 (stderr) drd/tests/pth_barrier_thr_cr (stderr) drd/tests/pth_detached3 (stderr) drd/tests/swapcontext (stderr) drd/tests/tls_threads (stderr) none/tests/fdleak_cat (stderr) - ppc64le https://kojipkgs.fedoraproject.org/packages/valgrind/3.28.0/0.1.RC1.fc46/data/logs/ppc64le/build.log == 813 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == drd/tests/pth_detached3 (stderr) none/tests/fdleak_cat (stderr) - s390x https://kojipkgs.fedoraproject.org/packages/valgrind/3.28.0/0.1.RC1.fc46/data/logs/s390x/build.log == 917 tests, 4 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 1 post failure == helgrind/tests/tc22_exit_w_lock (stderr) drd/tests/pth_detached3 (stderr) drd/tests/tc04_free_lock (stderr) none/tests/fdleak_cat (stderr) There is indeed a file descriptor "leak" in the latest coreutils cat. So this isn't a valgrind bug. Most others look the same as for 3.27.1. Most aarch64 failures have to do with slightly different backtraces. For i686 the fdleak_cmsg_supp and madv_guard need some inspection. _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
