public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/28937] New DSO dependency resolver buggyness with dlclose() Date: Mon, 08 Aug 2022 19:59:16 +0000 [thread overview] Message-ID: <bug-28937-131-U7pY3nCsFY@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28937-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28937 Sam James <sam at gentoo dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sam at gentoo dot org -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-08 19:59 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-03 12:48 [Bug dynamic-link/28937] New: " pieterjan.briers at gmail dot com 2022-03-03 15:08 ` [Bug dynamic-link/28937] " fweimer at redhat dot com 2022-03-03 15:27 ` fweimer at redhat dot com 2022-03-03 22:55 ` pieterjan.briers at gmail dot com 2022-03-03 23:25 ` pieterjan.briers at gmail dot com 2022-03-04 1:07 ` pieterjan.briers at gmail dot com 2022-03-11 19:24 ` freswa at archlinux dot org 2022-04-11 23:19 ` woodard at redhat dot com 2022-04-12 10:29 ` fweimer at redhat dot com 2022-08-08 10:38 ` fweimer at redhat dot com 2022-08-08 19:59 ` sam at gentoo dot org [this message] 2022-08-14 20:06 ` pieterjan.briers at gmail dot com 2022-08-15 9:23 ` [Bug dynamic-link/28937] New DSO dependency sorter does not put new map first if in a cycle fweimer at redhat dot com 2022-09-20 9:07 ` fweimer at redhat dot com 2022-09-21 9:17 ` fweimer at redhat dot com 2023-08-22 10:49 ` 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-28937-131-U7pY3nCsFY@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: 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).