public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drepper.fsp at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/12561] ld.so: dlclose() can remove required local scope elements of NODELETE linkmaps Date: Sun, 10 Apr 2011 20:02:00 -0000 [thread overview] Message-ID: <bug-12561-131-i879sUxRSM@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-12561-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=12561 Ulrich Drepper <drepper.fsp at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING --- Comment #2 from Ulrich Drepper <drepper.fsp at gmail dot com> 2011-04-10 20:02:22 UTC --- That test case doesn't show any bug. If you you use the handle for a dlopen'ed object to look up an object, then close the object, and finally use the returned function it is bound to fail. Whether the symbol has been found in a different object doesn't matter. You have to provide a valid test case. -- 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 prev parent reply other threads:[~2011-04-10 20:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-10 2:20 [Bug libc/12561] New: " pasky at suse dot cz 2011-03-22 1:41 ` [Bug libc/12561] " pasky at suse dot cz 2011-04-10 20:02 ` drepper.fsp at gmail dot com [this message] 2011-05-25 15:16 ` matz at suse dot de 2011-05-25 19:29 ` aj at suse dot de 2012-02-21 2:10 ` [Bug ld.so|libdl/12561] " jsm28 at gcc dot gnu.org 2012-03-30 14:13 ` [Bug dynamic-link/12561] " idoenmez at suse dot de 2012-10-23 17:34 ` ldv at altlinux dot org 2012-10-25 14:08 ` matz at suse dot de 2012-10-25 17:14 ` schwab@linux-m68k.org 2012-11-28 10:46 ` schwab@linux-m68k.org 2014-06-27 13:46 ` 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-12561-131-i879sUxRSM@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).