On Thu, Sep 24, 2020 at 03:40:54PM +0200, mwilck@xxxxxxxx wrote: > From: Martin Wilck <mwilck@xxxxxxxx> > Git complains about the extra blank line at the end of the file third-party/valgrind/mpath-tools.supp:33: new blank line at EOF. -Ben > These leaks are caused by other libraries (libsystemd, glibc, > libgcrypt) and should be ignored when debugging with valgrind > > Usage example: > > valgrind --suppressions=mpath-tools.supp \ > --leak-check=full --show-leak-kinds=all $COMMAND > > Signed-off-by: Martin Wilck <mwilck@xxxxxxxx> > --- > third-party/valgrind/mpath-tools.supp | 33 +++++++++++++++++++++++++++ > 1 file changed, 33 insertions(+) > create mode 100644 third-party/valgrind/mpath-tools.supp > > diff --git a/third-party/valgrind/mpath-tools.supp b/third-party/valgrind/mpath-tools.supp > new file mode 100644 > index 0000000..621463a > --- /dev/null > +++ b/third-party/valgrind/mpath-tools.supp > @@ -0,0 +1,33 @@ > +{ > + glibc _dlerror_run leak: https://stackoverflow.com/questions/1542457/memory-leak-reported-by-valgrind-in-dlopen > + Memcheck:Leak > + match-leak-kinds: reachable > + fun:calloc > + fun:_dlerror_run > + fun:dlopen* > +} > + > +{ > + systemd mempools are never freed: https://bugzilla.redhat.com/show_bug.cgi?id=1215670 > + Memcheck:Leak > + match-leak-kinds: reachable > + fun:malloc > + fun:mempool_alloc_tile > + fun:mempool_alloc0_tile > + fun:hashmap_base_new > + fun:hashmap_base_ensure_allocated > +} > + > +{ > + libgcrypt library initialization > + Memcheck:Leak > + match-leak-kinds: reachable > + fun:malloc > + ... > + fun:_gcry_xmalloc > + ... > + fun:global_init.* > + ... > + fun:_dl_init > +} > + > -- > 2.28.0 -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel