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

First of 3 replies, probably.

I'll start with Solaris and illumos. In short, all is well and even a 
bit better than 3.26.

Oracle Solaris 11.4 CBE 11.4.90
== 955 tests, 44 stderr failures, 1 stdout failure, 1 stderrB failure, 4 
stdoutB failures, 5 post failures ==
Most fails are due to a warning about reading debuginfo from 
libsocket.so.1 and libnsl.so.1. These are now just redirects to 
libc. I've retired my old HP workstation that was running Solaris 11.3 
so I don't use Oracle Solaris much at all these days. I fixed one nasty 
bug in the client stack creation (517697) and Oracle provided a patch 
for getsetcontext on the the latest Solaris versions (517697).  
Otherwise it looks mainly like a lack of care and attention - minor 
callstack diffs.

OpenIndiana Hipster 2025.10
== 918 tests, 5 stderr failures, 0 stdout failures, 1 stderrB failure, 3 
stdoutB failures, 0 post failures ==

OmniOS r151057
== 938 tests, 6 stderr failures, 0 stdout failures, 1 stderrB failure, 3 
stdoutB failures, 0 post failures ==

For both of the 2 illumos spins above there are 3 gdbserver tests that 
always fail and 3 DRD pthread_barrier tests that fail often but are 
intermittent.

Lastly there's one Helgrind test that was failing due to a 
pthread_rwlock_init callstack diff. I fixed that yesterday.

Next up, FreeBSD.

A+

Paul