From: Andreas Schwab <schwab@redhat.com>
To: Ulrich Drepper <drepper@gmail.com>
Cc: libc-hacker@sourceware.org
Subject: Re: [PATCH] Fix memory leak on init/fini dependency list
Date: Wed, 22 Sep 2010 15:00:00 -0000 [thread overview]
Message-ID: <m339t1vn6f.fsf@hase.home> (raw)
In-Reply-To: <AANLkTinvyKDefL6vQn8TCTDvx3tArXf6CzDagSEgqGkD@mail.gmail.com> (Ulrich Drepper's message of "Wed, 22 Sep 2010 07:12:15 -0700")
Ulrich Drepper <drepper@gmail.com> writes:
> On Wed, Sep 22, 2010 at 06:03, Andreas Schwab <schwab@redhat.com> wrote:
>> valgrind reports a memory leak when a program dlopens a library already
>> loaded as a direct dependency
>
> Test case?!
#include <stdlib.h>
#include <stdio.h>
#include <dlfcn.h>
int
main (int argc, char **argv)
{
void *handle = dlopen ("libc.so.6", RTLD_LAZY);
if (!handle)
{
fprintf (stderr, "%s\n", dlerror ());
return 1;
}
dlclose (handle);
}
Andreas.
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
prev parent reply other threads:[~2010-09-22 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 13:03 Andreas Schwab
[not found] ` <AANLkTinvyKDefL6vQn8TCTDvx3tArXf6CzDagSEgqGkD@mail.gmail.com>
2010-09-22 15:00 ` Andreas Schwab [this message]
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=m339t1vn6f.fsf@hase.home \
--to=schwab@redhat.com \
--cc=drepper@gmail.com \
--cc=libc-hacker@sourceware.org \
/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: link
Be 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).