public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/29528] __libc_early_init not called after dlmopen that reuses namespace
Date: Mon, 29 Aug 2022 13:47:54 +0000 [thread overview]
Message-ID: <bug-29528-131-KgB1VT7qIm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29528-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29528
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugzilla.redhat.com
| |/show_bug.cgi?id=2121746
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-29 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 11:22 [Bug dynamic-link/29528] New: __libc_early_init not called after dlmopen fweimer at redhat dot com
2022-08-26 11:22 ` [Bug dynamic-link/29528] " fweimer at redhat dot com
2022-08-26 11:26 ` [Bug dynamic-link/29528] __libc_early_init not called after dlmopen that reuses namespace fweimer at redhat dot com
2022-08-26 13:52 ` fweimer at redhat dot com
2022-08-26 19:45 ` fweimer at redhat dot com
2022-08-29 13:47 ` fweimer at redhat dot com [this message]
2022-09-22 14:39 ` al_95 at outlook dot it
2022-09-22 14:58 ` fweimer at redhat dot com
2022-10-14 9:02 ` cvs-commit at gcc dot gnu.org
2022-10-14 9:29 ` cvs-commit at gcc dot gnu.org
2022-10-14 10:37 ` cvs-commit at gcc dot gnu.org
2022-10-14 11:03 ` cvs-commit at gcc dot gnu.org
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-29528-131-KgB1VT7qIm@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: 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).