A brief look at libc6 source code indicates that perhaps any call to
_dl_catch_error may give rise to these valgrind warnings. The valgrind
suppressions I indicated above may not be sufficient in that case to catch all
dl-related valgrind warnings. You can probably suppress all these valgrind
warnings with the following:
{
dl_catch_error-leak
Memcheck:Leak
...
fun:_dl_catch_error
...
}
I'm no expert in either the glibc codebase or valgrind, so please evaluate this
workaround for yourself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883775
Title:
non cumulative memory leak in dlopen/dlclose
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/883775/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
