Same idea as for mips. sem_post does not fail on s390

[ambi/valgrind.git] / darwin9.supp

diff --git a/darwin9.supp b/darwin9.supp
index 0689e5de5aef9f346e5fc2cd659d18c8ee39c13c..f7769c7c5bfd5abbaa1d73cf3527625584b4bc1d 100644 (file)
--- a/darwin9.supp
+++ b/darwin9.supp
@@ -97,8 +97,17 @@
    fun:main
 }
 
+# afaict this is legit.  Might be caused by setenv("VAR=")
+# where the value string is empty (not sure)
 {
-   futimes-1
+   macos-Cond-7
+   Memcheck:Cond
+   fun:__setenv
+   fun:putenv*
+}
+
+{
+   macos-futimes-1
    Memcheck:Param
    futimes(tvp[1])
    fun:futimes
@@ -156,12 +165,44 @@
 # See https://bugs.kde.org/show_bug.cgi?id=188572 about this;  it's
 # unavoidable due to BSD setenv() semantics.
 {
-   <insert a suppression name here>
+   macos-__setenv-leak-see-our-bug-188572
    Memcheck:Leak
    fun:malloc_zone_malloc
    fun:__setenv
    fun:setenv$UNIX2003
 }
+{
+   macos-localeconv-leak
+   Memcheck:Leak
+   fun:malloc
+   fun:localeconv_l
+   fun:__vfprintf
+   fun:vsnprintf
+}
+
+{
+   macos-TFontFeatures::TFontFeatures(unsigned long)-uninitialised-stack-val
+   Memcheck:Cond
+   fun:_ZN13TFontFeaturesC2Em
+   fun:_ZNK9TBaseFont12CopyFeaturesEv
+}
+
+# Conditional jump or move depends on uninitialised value(s)
+#    at 0x4E5CD59: _DPSNextEvent (in /System/Library/Frameworks
+#                  /AppKit.framework/Versions/C/AppKit)
+#    by 0x4E5BF87: -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
+#                  (in /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit)
+#    by 0x4E54F9E: -[NSApplication run] (in /System/Library/Frameworks
+#                  /AppKit.framework/Versions/C/AppKit)
+#  Uninitialised value was created by a stack allocation
+#    at 0x4E5C450: _DPSNextEvent (in /System/Library/Frameworks
+#                                    /AppKit.framework/Versions/C/AppKit)
+{
+   macos-_DPSNextEvent-stack-allocated-uninit
+   Memcheck:Cond
+   fun:_DPSNextEvent
+}
+
 
 ##----------------------------------------------------------------------##
 # Helgrind
@@ -200,33 +241,57 @@
 # These ones were necessary to give no errors on a tiny threaded program.
 # I don't know if they're real problems or false positives (njn).
 
+#{
+#   helgrind-darwinlibc-nuke-everything-in-dyld
+#   Helgrind:Race
+#   obj:/usr/lib/dyld
+#}
+
 {
-   crude1
-   Helgrind:Race
-   obj:/usr/lib/dyld
-}
-{
-   crude2
+   helgrind-darwinlibc-nuke-everything-in-libSystem.B.dylib
    Helgrind:Race
    obj:/usr/lib/libSystem.B.dylib
 }
+
 # This would be better as "fun:\?\?\?" but string matching doesn't seem to
 # allow escaping meta-chars.
+#
+# This is very bad .. not only will it hide races in any
+# un-identified piece of code, the ??? also matches any 3-char
+# function name.
 {
-   crude3
+   helgrind-darwinlibc-nuke-everything-in-???-(unknown-code)
    Helgrind:Race
    fun:???
 }
+
 {
-   crude4
+   helgrind-darwinlibc--mythread_wrapper-*thread*start*
    Helgrind:Race
    fun:mythread_wrapper
+   fun:*thread*start*
 }
+
 {
-   crude5
+   helgrind-darwinlibc--pthread_create_WRK-pthread_create
    Helgrind:Race
-   ...
    fun:pthread_create_WRK
    fun:pthread_create
 }
 
+
+# Thread #9: Bug in libpthread: recursive write lock granted on 
+#            mutex/wrlock which does not support recursion
+#  at 0x18696: pthread_cond_wait* (hg_intercepts.c:655)
+#  by 0x2300B8: pthread_rwlock_wrlock$UNIX2003 (in /usr/lib/libSystem.B.dylib)
+#  by 0x18F41: pthread_rwlock_wrlock* (hg_intercepts.c:1177)
+#
+# no idea what this is about
+#
+{
+   helgrind-darwin9--pthread-rwlock-kludgery
+   Helgrind:Misc
+   fun:pthread_cond_wait*
+   fun:pthread_rwlock_*lock*
+   fun:pthread_rwlock_*lock*
+}