From d5f9a5fffd77b3f00ba29d685fc720ad9268b7a5 Mon Sep 17 00:00:00 2001
From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
Date: Tue, 4 Jun 2019 13:39:00 -0400
Subject: [PATCH] supp: Ignore leaks caused by shout/sethostent

sethostent() seems to be using a global state and we endup with leaks from
that API when called through shout_init(). We had the option to only
ignore the shout case, but the impression is that if we have shout and
another sethostend user, as it's a global state, we may endup with a
different stack trace for the same leak. So in the end, we just ignore
memory allocated by sethostent in general.
---
 tests/check/gst-plugins-good.supp | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/tests/check/gst-plugins-good.supp b/tests/check/gst-plugins-good.supp
index c9ea5e4..5132c7d 100644
--- a/tests/check/gst-plugins-good.supp
+++ b/tests/check/gst-plugins-good.supp
@@ -205,3 +205,12 @@
   fun:g_tls_certificate_gnutls_real_copy
   fun:g_tls_server_connection_gnutls_retrieve_function
 }
+
+{
+  <shout leaks through sethostent, ignoring all sethostent leaks as this is using global>
+  Memcheck:Leak
+  match-leak-kinds: definite
+  fun:malloc
+  ...
+  fun:sethostent
+}
-- 
2.7.4