public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hpa at zytor dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/27880] Please provide a pthread pid accessor
Date: Tue, 18 May 2021 05:05:54 +0000 [thread overview]
Message-ID: <bug-27880-131-jh1ULYsWbk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27880-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27880
--- Comment #1 from hpa at zytor dot com <hpa at zytor dot com> ---
>From what I can read, MacOS X seems to have a pthread_threadid_np(thread, &tid)
interface for this purpose; AIX has can get it via the pthread_getthrds_np()
interface.
FreeBSD has pthread_getthreadid_np(), but that only applies to the self thread,
i.e. is equivalent to Linux gettid().
Reusing the MacOS X interface seems most sensible; the pthread_getthrds_np()
interface seems very complex.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-05-18 5:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 1:19 [Bug nptl/27880] New: " hpa at zytor dot com
2021-05-18 5:05 ` hpa at zytor dot com [this message]
2021-05-18 18:36 ` [Bug nptl/27880] " joseph at codesourcery dot com
2021-05-18 19:31 ` hpa at zytor dot com
2021-05-18 20:58 ` adhemerval.zanella at linaro dot org
2021-05-19 20:14 ` fweimer at redhat dot com
2021-05-19 20:21 ` hpa at zytor dot com
2021-05-19 20:27 ` adhemerval.zanella at linaro dot org
2021-05-19 20:31 ` hpa at zytor dot com
2021-05-19 20:49 ` fweimer at redhat dot com
2021-05-19 22:50 ` mtk.manpages at gmail dot com
2021-05-27 19:32 ` adhemerval.zanella at linaro dot org
2021-05-27 23:48 ` hpa at zytor dot com
2023-04-14 3:50 ` sam at gentoo dot org
2024-02-06 22:30 ` jkriegshauser 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-27880-131-jh1ULYsWbk@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).