From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org, kevinb@redhat.com
Subject: Re: [PATCH v3 11/11] Add TLS NEWS entry and document 'set force-internal-tls-address-lookup' command
Date: Fri, 25 Oct 2024 10:34:49 +0300 [thread overview]
Message-ID: <8634kkd49y.fsf@gnu.org> (raw)
In-Reply-To: <20241025033431.36274-12-kevinb@redhat.com> (message from Kevin Buettner on Thu, 24 Oct 2024 19:26:29 -0700)
> From: Kevin Buettner <kevinb@redhat.com>
> Cc: Kevin Buettner <kevinb@redhat.com>
> Date: Thu, 24 Oct 2024 19:26:29 -0700
>
> ---
> gdb/NEWS | 20 ++++++++++++++++++
> gdb/doc/gdb.texinfo | 50 +++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 70 insertions(+)
Thanks, this is okay, provided you fix the following nit:
> +cross-debugging scenarios or when debugging programs that are linked
> +in such a way that @code{libthread_db} support is unavailable - this
^^^
Please use "--", not a single dash, as the result will look better in
print.
> +This command is only available for @sc{gnu}/Linux targets. Its
> +primary use is for testing - certain tests in the @value{GDBN} test
Likewise.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
prev parent reply other threads:[~2024-10-25 7:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 2:26 [PATCH v3 00/11] GDB-internal TLS support for Linux targets Kevin Buettner
2024-10-25 2:26 ` [PATCH v3 01/11] Don't attempt to find TLS address when target has no registers Kevin Buettner
2024-10-25 2:26 ` [PATCH v3 02/11] Allow TLS access to work in gdb.server/no-thread-db.exp Kevin Buettner
2024-10-25 2:26 ` [PATCH v3 03/11] Track and fetch TLS module ids for MUSL and GLIBC Kevin Buettner
2024-10-25 2:26 ` [PATCH v3 04/11] Implement internal TLS address lookup for Linux targets Kevin Buettner
2024-10-25 2:26 ` [PATCH v3 05/11] Internal TLS support for aarch64, x86_64, riscv, ppc64, and s390x Kevin Buettner
2024-10-25 2:26 ` [PATCH v3 06/11] Internal, but disabled, TLS support for i386 Kevin Buettner
2024-10-25 2:26 ` [PATCH v3 07/11] Delete disabled i386 internal TLS support Kevin Buettner
2024-10-25 2:26 ` [PATCH v3 08/11] New test - gdb.base/tls-nothreads.exp Kevin Buettner
2024-10-25 2:26 ` [PATCH v3 09/11] New test - gdb.base/tls-multiobj.exp Kevin Buettner
2024-10-25 2:26 ` [PATCH v3 10/11] New test - gdb.base/tls-dlobj.exp Kevin Buettner
2024-10-25 2:26 ` [PATCH v3 11/11] Add TLS NEWS entry and document 'set force-internal-tls-address-lookup' command Kevin Buettner
2024-10-25 7:34 ` Eli Zaretskii [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=8634kkd49y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.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.
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).