From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH 0/3] ntpl: Export libthread_db-used symbols (v2)
Date: Mon, 28 Jun 2021 08:30:57 -0400 [thread overview]
Message-ID: <303c06b6-63c9-43e8-1da3-18976ab967f3@redhat.com> (raw)
In-Reply-To: <cover.1624871226.git.fweimer@redhat.com>
On 6/28/21 5:09 AM, Florian Weimer via Libc-alpha wrote:
> This incorporates Carlos' feedback and adds more symbol tests to the
> GLIBC_PRIVATE consistency check.
>
> Tested on x86_64-linux-gnu, i686-linux-gnu, built with
> build-many-glibcs.py. Not yet tested with GDB.
Thanks for moving this forward, and ensuring that the additional symbols
help ensure that gdb can handle the new integration of libpthread into
libc.
> Florian Weimer (3):
> nptl_db: Clean up main/rtld variable handling
> nptl: Rename nptl_version to __nptl_version
> nptl: Export libthread_db-used symbols under GLIBC_PRIVATE
>
> nptl/Versions | 58 ++++++++++++++++++++++++++++++++++++++++++
> nptl/pthread_create.c | 13 ++++++----
> nptl_db/Makefile | 2 +-
> nptl_db/db-symbols.awk | 17 ++++++++++---
> nptl_db/structs.def | 16 +++++-------
> nptl_db/td_ta_new.c | 2 +-
> 6 files changed, 88 insertions(+), 20 deletions(-)
>
--
Cheers,
Carlos.
prev parent reply other threads:[~2021-06-28 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 9:09 Florian Weimer
2021-06-28 9:09 ` [PATCH 1/3] nptl_db: Clean up main/rtld variable handling Florian Weimer
2021-06-28 12:31 ` Carlos O'Donell
2021-06-28 9:09 ` [PATCH 2/3] nptl: Rename nptl_version to __nptl_version Florian Weimer
2021-06-28 12:31 ` Carlos O'Donell
2021-06-28 9:09 ` [PATCH 3/3] nptl: Export libthread_db-used symbols under GLIBC_PRIVATE Florian Weimer
2021-06-28 12:32 ` Carlos O'Donell
2021-06-28 12:30 ` Carlos O'Donell [this message]
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=303c06b6-63c9-43e8-1da3-18976ab967f3@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).