summaryrefslogtreecommitdiff
path: root/script/valgrind.supp
diff options
context:
space:
mode:
authorPatrick Steinhardt <ps@pks.im>2019-09-21 17:55:54 +0200
committerPatrick Steinhardt <ps@pks.im>2019-09-21 18:21:47 +0200
commit56d5b4432b3274755ab40cdc0213d68989214b76 (patch)
treee07e18a2f45cdea0e34d313566fd67a7bd452bd3 /script/valgrind.supp
parent68cfb580e19c419992ba0b0a299e5fd6dc60ed99 (diff)
downloadlibgit2-56d5b4432b3274755ab40cdc0213d68989214b76.tar.gz
valgrind: suppress memory leaks in libssh2_session_handshake
On Ubuntu, the combination of libgcrypt and libssh2 is quite old and known to contain memory leaks. We thus have several functions listed in our suppressions file that are known to leak. Due to a recent update of libssh2 or libgcrypt, there now are new memory leaks caused by libssh2_session_handshake and libssh2_init that cause the CI to fail. Add a new suppression to fix the issue.
Diffstat (limited to 'script/valgrind.supp')
-rw-r--r--script/valgrind.supp20
1 files changed, 20 insertions, 0 deletions
diff --git a/script/valgrind.supp b/script/valgrind.supp
index b74791974..6ea687ab9 100644
--- a/script/valgrind.supp
+++ b/script/valgrind.supp
@@ -56,6 +56,15 @@
}
{
+ ignore-libssh2-init
+ Memcheck:Leak
+ ...
+ fun:gcry_control
+ fun:libssh2_init
+ ...
+}
+
+{
ignore-libssh2-gcrypt-control-leak
Memcheck:Leak
...
@@ -104,6 +113,17 @@
}
{
+ ignore-libssh2-gcrypt-session-handshake
+ Memcheck:Leak
+ ...
+ obj:*libgcrypt.so*
+ obj:*libssh2.so*
+ obj:*libssh2.so*
+ fun:libssh2_session_handshake
+ ...
+}
+
+{
ignore-noai6ai_cached-double-free
Memcheck:Free
fun:free