This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/13123] New: dlopen() leaks 8 bytes on each time used against regular binary like /bin/ls
- From: "itakingiteasy at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Tue, 23 Aug 2011 15:42:26 +0000
- Subject: [Bug libc/13123] New: dlopen() leaks 8 bytes on each time used against regular binary like /bin/ls
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13123
Bug #: 13123
Summary: dlopen() leaks 8 bytes on each time used against
regular binary like /bin/ls
Product: glibc
Version: 2.12
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper.fsp@gmail.com
ReportedBy: itakingiteasy@gmail.com
Classification: Unclassified
Created attachment 5908
--> http://sourceware.org/bugzilla/attachment.cgi?id=5908
Simple testcase reproducing the bug
This is might be a false positive, but valgrind reports about leak of 8 bytes
each time dlopen() called aginst regular binary like /bin/ls. I am attaching
simple test-case illustrating the problem - each time it's load() function
called valgrind reports about additional 8 bytes lost.
My system is Gentoo/amd64/libc-2.12 (but same problem is also exists on my x86
gentoo notebook and was confirmed by many people on irc with various distros
and glibc versions).
Noteworthy that this valgrind report can be avoidid by using tcmalloc/jemalloc
instead of regular glibc malloc.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.