From: Florian Weimer <fw@deneb.enyo.de>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "Rich Felker" <dalias@libc.org>, Арсений <a@saur0n.science>,
musl@lists.openwall.com
Subject: Re: [musl] Mutexes are not unlocking
Date: Mon, 23 Nov 2020 18:18:47 +0100 [thread overview]
Message-ID: <87o8jo3saw.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20201123171016.GV1312820@redhat.com> (Jonathan Wakely's message of "Mon, 23 Nov 2020 17:10:16 +0000")
* Jonathan Wakely:
> Yes. I don't remember why but maybe pthread_key_create exists as a
> stub in glibc's libc.so and so __pthread_key_create is used to
> **really** detect that libpthread.so is linked in.
There's no pthread_key_create in libc. Roland actually added a
comment why __pthread_key_create is used:
+/* For a program to be multi-threaded the only thing that it certainly must
+ be using is pthread_create. However, there may be other libraries that
+ intercept pthread_create with their own definitions to wrap pthreads
+ functionality for some purpose. In those cases, pthread_create being
+ defined might not necessarily mean that libpthread is actually linked
+ in.
I believe the Boehm/Demers/Weiser garbage collector used to be one of
these libraries.
next prev parent reply other threads:[~2020-11-23 17:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 5:25 a
2020-11-20 5:58 ` Rich Felker
2020-11-21 6:46 ` Re[2]: " a
2020-11-21 15:51 ` Rich Felker
2020-11-22 18:43 ` Re[2]: " Арсений
2020-11-22 19:11 ` Rich Felker
2020-11-22 19:23 ` Florian Weimer
2020-11-22 19:28 ` Rich Felker
2020-11-22 19:45 ` Re[2]: " Арсений
2020-11-22 20:05 ` Арсений
2020-11-23 12:24 ` Jonathan Wakely
2020-11-23 14:56 ` Rich Felker
2020-11-23 16:58 ` Jonathan Wakely
2020-11-23 11:41 ` Jonathan Wakely
2020-11-23 14:53 ` Rich Felker
2020-11-23 16:19 ` Jonathan Wakely
2020-11-23 16:51 ` Rich Felker
2020-11-23 17:10 ` Jonathan Wakely
2020-11-23 17:18 ` Florian Weimer [this message]
2020-11-23 16:59 ` Florian Weimer
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=87o8jo3saw.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=a@saur0n.science \
--cc=dalias@libc.org \
--cc=jwakely@redhat.com \
--cc=musl@lists.openwall.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).