Commit f227f659 authored by Nicolas Dufresne's avatar Nicolas Dufresne

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.
parent dbd5d5b2
......@@ -205,3 +205,12 @@
<shout leaks through sethostent, ignoring all sethostent leaks as this is using global>
match-leak-kinds: definite
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment