From: Paul Floyd <pjfloyd@wanadoo.fr>
Date: Fri, 19 Dec 2025 05:58:51 +0000 (+0100)
Subject: Bug 258140 - Valgrind on OS X always reports some memory "still reachable"
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8a95c48c80de40199eba5d8e6119f27bb84a50b9;p=thirdparty%2Fvalgrind.git

Bug 258140 - Valgrind on OS X always reports some memory "still reachable"

Just needed one more suppression for the minimal test in the bugzilla
item. I expect that there will be a seemingly endless number of leaks
in Darwin (different libs, later versions).
---

diff --git a/NEWS b/NEWS
index b8e15e0df..6360e83a5 100644
--- a/NEWS
+++ b/NEWS
@@ -29,6 +29,7 @@ than mailing the developers (or mailing lists) directly -- bugs that
 are not entered into bugzilla tend to get forgotten about or ignored.
 
 228343  none/tests/darwin/bug228343 fails on OS X
+258140  Valgrind on OS X always reports some memory "still reachable"
 413369  unhandled amd64-darwin syscall: unix:151 (getpgid)
 487055  memcheck/tests/x86-linux/scalar fails running in Docker
 509562  s390x: Define minimum required machine model
diff --git a/darwin.supp b/darwin.supp
index 1f693d6b2..f256a3a06 100644
--- a/darwin.supp
+++ b/darwin.supp
@@ -783,8 +783,16 @@
 # I suppose that this is deliberate
 # and that Apple know what they are doing?
 {
-   masOS1015:__chkstk_darwin_probe
+   macOS1015:__chkstk_darwin_probe
    Memcheck:Addr8
    fun:__chkstk_darwin_probe
 }
 
+{
+   macOS1015:_mh_execute_header
+   Memcheck:Leak
+   match-leak-kinds: definite
+   fun:malloc
+   fun:_mh_execute_header
+}
+