Same issue seen with valgrind while developing on Vulkan core.
Bug related on github here :
https://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers/issues/1298
** Bug watch added:
github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers/issues #1298
https://github.com/KhronosGroup/Vul
** Changed in: valgrind (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160352
Title:
Still reachable leak is reported with dlopen and pthread
To manage n
** Changed in: valgrind (Debian)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160352
Title:
Still reachable leak is reported with dlopen and pthread
To manage n
** Changed in: valgrind (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160352
Title:
Still reachable leak is reported with dlopen and pthread
To mana
Fixed independently in Debian, and making its way into saucy now via a
merge. Thanks.
valgrind (1:3.8.1-3ubuntu1) saucy; urgency=low
* Resynchronise with Debian. Remaining changes:
- Allow specification of an extra directory in which to look for
debuginfo objects.
- Remove valgr
** Description changed:
Valgrind reports still reachable leaks in dlopen()/dlclose() only when
linked with -lpthread with the following code:
- $ cat /tmp/valgrind-dlopen-pthread-leak.c
+ $ cat /tmp/valgrind-dlopen-pthread-leak.c
#include
#include
int main() {
- char *error =
