public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "itakingiteasy at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13123] New: dlopen() leaks 8 bytes on each time used against regular binary like /bin/ls Date: Tue, 23 Aug 2011 15:43:00 -0000 [thread overview] Message-ID: <bug-13123-131@http.sourceware.org/bugzilla/> (raw) 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.
next reply other threads:[~2011-08-23 15:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-23 15:43 itakingiteasy at gmail dot com [this message] 2011-09-08 2:47 ` [Bug libc/13123] " drepper.fsp at gmail dot com 2011-09-08 2:59 ` drepper.fsp at gmail dot com 2014-06-27 12:16 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-13123-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).