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.
Showing with 9 additions and 0 deletions