Bug#318317: libc6: Numerous (49) memory leaks in gethostbyname, as reported by mudflap

["Vesselin Peev" <vesselinpeev@hotmail.com>]

Jakub Jelinek from Red Hat said the following:

"glibc doesn't free memory unnecessarily on program exit, only when using
memory leak checking tools like mtrace or valgrind it will free all its
internal buffers."

I know the problem is not present with valgrind on Debian, too, so the above 
then holds for the Debian libc package, too. From his words one can conclude 
that there must be a better integration between mudflap and glibc.