X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/e8d0f23a1cdda93619b38596bebbdc0c58a05160..34b1612aaf4fb4375dc39f42941027e56b80aafa:/tools/simgrid.supp

diff --git a/tools/simgrid.supp b/tools/simgrid.supp
index 82cd7a8293..98a18e1575 100644
--- a/tools/simgrid.supp
+++ b/tools/simgrid.supp
@@ -15,23 +15,18 @@
    obj:/usr/bin/*
 }
 
-# There's a constant leak of 56 bytes in the depths of libc which
-# manifests, for example, when using backtrace()
 {
-   Memory leak in libc/dlopen with -pthread
+   Memory leak in cmake
    Memcheck:Leak
-   fun:malloc
-   fun:_dl_map_object_deps
-   fun:dl_open_worker
-   fun:_dl_catch_error
-   fun:_dl_open
-   fun:do_dlopen
-   fun:_dl_catch_error
-   fun:dlerror_run
-   fun:__libc_dlopen_mode
+   match-leak-kinds:reachable
+   ...
+   fun:_ZN4Json5Value13nullSingletonEv
+   obj:*/libjsoncpp.so*
+   ...
+   fun:_dl_init
 }
 
-# Another problem in glibc, where makecontext does not reset the EBP register,
+# There's problem in glibc, where makecontext does not reset the EBP register,
 # and backtrace goes too far when walking up the stack frames
 {
    Invalid read in backtrace, called after makecontext
@@ -51,6 +46,14 @@
    fun:_dl_start
 }
 
+# There are memory leaks when using dlopen
+{
+   Memory leak in libc/dlopen
+   Memcheck:Leak
+   ...
+   fun:_dlerror_run
+}
+
 # 72704 bytes leak from GCC >5.1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64535
 {
    Memory leak in dl_init
@@ -63,6 +66,17 @@
    fun:_dl_init
 }
 
+{
+   Leaks in test-help-version and test-help-logs (early call to exit())
+   Memcheck:Leak
+   match-leak-kinds: reachable
+   fun:_Znwm
+   fun:_ZN7simgrid3s4u6EngineC1EPiPPc
+   fun:main
+   ...
+   obj:*/basic-parsing-test
+}
+
 #Ignore leaks in SMPI sample codes
 {
    Leaks in SMPI sample codes
@@ -72,7 +86,16 @@
    fun:smpi_simulated_main_
 }
 
-# Memory leaks appearing to be in libcgraph.  They can be seen with the
+#This test has an intentional leak
+{
+   Intentional leak in SMPI sample codes
+   Memcheck:Leak
+   match-leak-kinds: all
+   fun:MPI_Comm_dup
+   obj:coll-allreduce-with-leaks*
+}
+
+#Memory leaks appearing to be in libcgraph.  They can be seen with the
 # following simple program:
 # ,----
 # | #include <stdio.h>
@@ -92,43 +115,34 @@
 # | }
 # `----
 {
-   Memory leak in libcgraph (1/2)
+   Memory leak in libcgraph (1/3)
    Memcheck:Leak
    fun:malloc
    ...
-   obj:/usr/lib/libcgraph.so*
    fun:aaglex
    fun:aagparse
    fun:agconcat
 }
 {
-   Memory leak in libcgraph (1/2)
+   Memory leak in libcgraph (2/3)
    Memcheck:Leak
    fun:calloc
    ...
-   obj:/usr/lib/libcgraph.so*
+   obj:*/libcgraph.so*
    fun:aagparse
    fun:agconcat
 }
 {
-   Memory leak in libcgraph (2/2)
+   Memory leak in libcgraph (3/3)
    Memcheck:Leak
    fun:malloc
    ...
    fun:agnode
-   obj:/usr/lib/libcgraph.so*
+   obj:*/libcgraph.so*
    fun:aagparse
    fun:agconcat
 }
 
-# We're not interested by memory leaks in the Lua interpreter
-{
-   Memory leak in lua
-   Memcheck:Leak
-   ...
-   fun:luaD_precall
-}
-
 # libunwind seems to be using msync poorly, thus triggering these
 # https://github.com/JuliaLang/julia/issues/4533
 {
@@ -139,3 +153,56 @@
    obj:*/libpthread*.so
    ...
 }
+
+{
+   ignore unwind cruft
+   Memcheck:Param
+   rt_sigprocmask(set)
+   ...
+   obj:/usr/lib/x86_64-linux-gnu/libunwind.so.*
+   ...
+}
+{
+   ignore unwind cruft
+   Memcheck:Param
+   msync(start)
+   ...
+   obj:/usr/lib/x86_64-linux-gnu/libunwind.so.*
+   ...
+}
+{
+   ignore unwind cruft
+   Memcheck:Param
+   write(buf)
+   ...
+   fun:_ULx86_64_step
+   obj:/usr/lib/x86_64-linux-gnu/libunwind.so.*
+}
+
+{
+   ignore unwind invalid reads
+   Memcheck:Addr8
+   fun:_Ux86_64_setcontext
+}
+
+# Ignore python cruft
+{
+   ignore python cruft 1
+   Memcheck:Cond
+   ...
+   obj:/usr/bin/python*
+}
+
+{
+   ignore python cruft 2
+   Memcheck:Addr4
+   ...
+   obj:/usr/bin/python*
+}
+
+{
+   ignore python cruft 3
+   Memcheck:Value8
+   ...
+   obj:/usr/bin/python*
+}