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.
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
