public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug dynamic-link/14511] dlclose DSO unloading fundamentally unsafe Date: Thu, 23 Aug 2012 12:04:00 -0000 [thread overview] Message-ID: <bug-14511-131-317KjbN3m0@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14511-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14511 Jakub Jelinek <jakub at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID --- Comment #7 from Jakub Jelinek <jakub at redhat dot com> 2012-08-23 12:04:00 UTC --- Doesn't matter what levels of libraries you have. It is users responsibility to ensure pointers to library code aren't accessed after library is unloaded. The default is correct, and has been that way since the beginning. -- 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:[~2012-08-23 12:04 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-22 22:24 [Bug dynamic-link/14511] New: " bugdal at aerifal dot cx 2012-08-22 22:27 ` [Bug dynamic-link/14511] " bugdal at aerifal dot cx 2012-08-22 22:30 ` bugdal at aerifal dot cx 2012-08-22 22:32 ` bugdal at aerifal dot cx 2012-08-23 5:24 ` ppluzhnikov at google dot com 2012-08-23 6:50 ` jakub at redhat dot com 2012-08-23 12:01 ` bugdal at aerifal dot cx 2012-08-23 12:04 ` jakub at redhat dot com [this message] 2014-06-17 5:54 ` fweimer at redhat dot com 2023-08-07 10:10 ` sam at gentoo dot org 2023-08-07 10:10 ` sam at gentoo dot org 2024-02-06 14:42 ` gabravier at gmail 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-14511-131-317KjbN3m0@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).