Re: [Valgrind-users] Valgrind-3.27.0.RC1 is available for testing

[Paul F. <pj...@wa...>]

On 2026-04-14 03:07, Mark Wielaard wrote:
> An RC1 tarball for 3.27.0 is now available at
> https://sourceware.org/pub/valgrind/valgrind-3.27.0.RC1.tar.bz2
> (md5sum = bd95111c1a9f81f136c5e4e2c62b493e)
> (sha1sum = 0eefb3a7d86a3bd0154480db3d2173bb8bd6d7c1)
> https://sourceware.org/pub/valgrind/valgrind-3.27.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
>
> An RC2 should be available Fri Apr 17
> The final 3.27.0 release is scheduled for Mon Apr 20.

Hi again

Second of three responses. FreeBSD.

In short, all looking good. The development version of FreeBSD always 
has some issues. It's nice to be able to access a couple of FreeBSD 
servers on GCC cfarm.

When FreeBSD 14.4-RELEASE came out there were no problems. 16.0-CURRENT 
(roughly the git head version) has been another kettle of fish. Two big 
problems, one due to switching to using the LLVM toolchain (instead of 
GNU ld.bfd) to generate split .debug files. The other, not specific to 
16 but I came across the issue on cfarm 16.0 servers, is that if GNU 
paltform-binutils is installed then clang will default to using ld.bfd 
rather than ld.lld. That broke my assumptions in parse_procselfmaps(). 
All that should be fixed.

amd64
======

FreeBSD 14.3-RELEASE-p8 amd64
== 964 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 1 
stdoutB failure, 0 post failures ==

FreeBSD 14.4-RELEASE-p1
== 941 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 
0 stdoutB failures, 0 post failures ==

FreeBSD 15.0-RELEASE-p5 amd64
== 967 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 1 
stdoutB failure, 0 post failures ==

FreeBSD 16.0-CURRENT amd64
== 961 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 
1 stdoutB failure, 0 post failures ==

arm64
=====

FreeBSD 15.0-RELEASE-p5 arm64
== 809 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 
stdoutB failures, 0 post failures ==

FreeBSD 16.0-CURRENT arm64
== 803 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 
1 stdoutB failure, 0 post failures ==

There are about 3 tests that are flaky and I see them failing 
always/regularly.

I need to look at drd/tests/tls_threads  on 16.0-CURRENT.


Next up, Darwin.

A+

Paul