From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: libc-alpha@sourceware.org, gdb-patches@sourceware.org,
Pedro Alves <pedro@palves.net>,
Kevin Buettner <kevinb@redhat.com>
Subject: Re: [PATCH glibc] nptl_db: different libpthread/ld.so load orders (bug 27744)
Date: Fri, 16 Apr 2021 20:35:21 +0200 [thread overview]
Message-ID: <87h7k6m61i.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <78edaf4c-e2f2-8d4e-0950-98ba24367921@polymtl.ca> (Simon Marchi's message of "Fri, 16 Apr 2021 13:33:26 -0400")
* Simon Marchi:
> Is it possible to have a completely static executable that doesn't use
> ld.so but uses pthreads?
Absolutely, the new nptl/tst-pthread-gdb-attach-static shows that TLS is
already supported in GDB.
(In v2 of the patch, the test will actually run …)
Thanks,
Florian
next prev parent reply other threads:[~2021-04-16 18:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 15:56 [PATCH glibc] nptl_db: different libpthread/ld.so load orders (bug 27744) Florian Weimer via Libc-alpha
2021-04-16 16:07 ` Simon Marchi via Libc-alpha
2021-04-16 16:12 ` Florian Weimer via Libc-alpha
2021-04-16 16:25 ` Pedro Alves via Libc-alpha
2021-04-16 16:28 ` Florian Weimer via Libc-alpha
2021-04-16 16:33 ` Pedro Alves
2021-04-16 16:43 ` Florian Weimer via Libc-alpha
2021-04-16 16:47 ` Pedro Alves via Libc-alpha
2021-04-16 16:53 ` Simon Marchi via Libc-alpha
2021-04-16 17:18 ` Pedro Alves
2021-04-16 17:26 ` Florian Weimer via Libc-alpha
2021-04-16 17:33 ` Simon Marchi via Libc-alpha
2021-04-16 18:29 ` Pedro Alves
2021-04-16 18:35 ` Florian Weimer via Libc-alpha [this message]
2021-04-16 17:28 ` Florian Weimer via Libc-alpha
2021-04-16 17:43 ` Pedro Alves
2021-04-19 9:06 ` Florian Weimer via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7k6m61i.fsf@oldenburg.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=pedro@palves.net \
--cc=simon.marchi@polymtl.ca \
/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).