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 all,

Part 3, Darwin.

A few issues, on macOS 11 to 13 I get.

m_mach/dyld_cache.c:45:10: fatal error: 'priv_dyld_internals.h' file not 
found #include "priv_dyld_internals.h" // CACHE_MAGIC_*, 
dyld_cache_header, etc ^~~~~~~~~~~~~~~~~~~~~~~ 1 error generated.

I just pushed a fix for that. There are a load of unexpected Massif 
failures on macOS 10.14. Not serious, I need to add more ignore functions.

General Darwin overview. In short, the Darwin port has gone from barely 
building on 10.13 to being half decent. There is still a great deal to do.

Good: many fixes for 10.13, added 10.14, 10.15, 11, 12, 13

Bad: No arm64 support yet - building Valgirnd on arm64 is even more 
difficult than on amd64. Helgrind and DRD have some encapsulation issues 
(things like internal mutexes, clearing or reinitialising mutexes/locks 
on fork). Small C and C++ only tests work quite well (like regtest). 
Real-world GUI apps and apps using Apple frameworks work very badly. At 
the very least they require huge numbers of suppressions. macOS 13 has 
about twice as many regtest failures as previous macOS versions (~80 
compared to ~40). Analysis is ongoing. x86 has unsupported opcode issues 
- a few on macOS 10.13 and macOS 10.14 x86 is unusable because they are 
used in dyld (the dynamic loader). macOS 10.15 dropped x86 support. No 
access to macOS 14 and later amd64 hardware or VMs. No access to macOS 
11 arm64. 12 and later can be installed in VMs fairly easily it seems. 
For regtest: Some problems with clang debuginfo. Many leaks on startup 
mess up memcheck leak tests and DHAT.

macOS 10.13 == 806 tests, 36 stderr failures, 12 stdout failures, 0 
stderrB failures, 0 stdoutB failures, 2 post failures == macOS 10.14 == 
748 tests, 50 stderr failures, 4 stdout failures, 8 stderrB failures, 7 
stdoutB failures, 32 post failures ==

macOS 10.15 == 748 tests, 36 stderr failures, 4 stdout failures, 7 
stderrB failures, 7 stdoutB failures, 2 post failures ==

macOS 11 macOS 12 macOS 13 Build failed

A+

Paul