Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 446712 [details] Simple use of ltopen/ltclose Description of problem: Using the dlopem/dlclose mechanism leads to a memory leak detected by valgrind. I attach a code snippet. How reproducible: Always. Steps to Reproduce: 1. Compile the code snippet: g++ -o lt lt.cpp -ldl 2. Run valgrind: valgrind --leak-check=full --show-reachable=yes --trace-children=yes ./lt 3. Check the valgrind report ("still reachable: 56 bytes in 1 blocks")
glibc-2.12.90-13 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/glibc-2.12.90-13
glibc-2.12.90-13 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update glibc'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/glibc-2.12.90-13
glibc-2.12.90-14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update glibc'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/glibc-2.12.90-14
glibc-2.12.90-14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
Just for the record, I tried in Fedora 14 and the bug has been fixed. Thank you.