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 nptl/24776] pthread_key_create, pthread_setspecific are incompatible with dlmopen
Date: Mon, 31 May 2021 18:10:22 +0000 [thread overview]
Message-ID: <bug-24776-131-Ovjbec5On4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24776-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24776
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
--- Comment #9 from Florian Weimer <fweimer at redhat dot com> ---
Bug 26955 raises the related issue that there is just mapping per thread from
key to data, but the data structure that maintains the keys is duplicated if
libc.so is loaded more than once.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-05-31 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-24776-131@http.sourceware.org/bugzilla/>
2021-04-21 19:40 ` fweimer at redhat dot com
2021-05-31 18:10 ` fweimer at redhat dot com [this message]
2021-05-31 18:10 ` fweimer at redhat dot com
2021-08-08 5:15 ` alxchk at gmail dot com
2021-08-08 11:06 ` sware at reimardoeffinger dot de
2021-11-20 16:37 ` ppluzhnikov at google dot com
2022-10-01 17:16 ` jadahl at gmail dot com
2023-04-24 12:17 ` kristofer.berggren 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-24776-131-Ovjbec5On4@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).