Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Kevin Buettner <kevinb@redhat.com>
Subject: [PATCH 11/11] Add TLS NEWS entry and document 'set force-internal-tls-address-lookup' command
Date: Wed,  9 Oct 2024 19:16:14 -0700	[thread overview]
Message-ID: <20241010022552.47637-12-kevinb@redhat.com> (raw)
In-Reply-To: <20241010022552.47637-1-kevinb@redhat.com>

---
 gdb/NEWS            | 20 ++++++++++++++++++++
 gdb/doc/gdb.texinfo | 17 +++++++++++++++++
 2 files changed, 37 insertions(+)

diff --git a/gdb/NEWS b/gdb/NEWS
index 42668cbc057..dcb24eb5248 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -63,6 +63,26 @@
      the return value from the latest "stepOut" command, when
      appropriate.
 
+* GDB-internal TLS support
+
+  ** Linux targets for the x86_64, aarch64, ppc64, s390x, and riscv
+     architectures now have GDB-internal support for TLS address
+     lookup in addition to that traditionally provided by the
+     libthread_db library.  This internal support works for programs
+     linked against either the GLIBC or MUSL C libraries.  For
+     programs linked against MUSL, this new internal support provides
+     new debug functionality, allowing access to TLS variables, due to
+     the fact that MUSL does not implement the libthread_db library. 
+     Internal TLS support is also useful in cross-debugging
+     situations, debugging statically linked binaries, and debugging
+     programs linked against GLIBC 2.33 and earlier, but which are not
+     linked against libpthread.
+
+  ** The command 'set force-internal-tls-address-lookup on' may be
+     used to force the internal TLS lookup mechanisms to be used.
+     Otherwise, TLS lookup via libthread_db will still be preferred,
+     when available.
+
 * New commands
 
 set style line-number foreground COLOR
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 46ca62ec0c3..f0f98061a1f 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -4067,6 +4067,23 @@ only on some platforms.
 @item show libthread-db-search-path 
 Display current libthread_db search path.
 
+@kindex set force-internal-tls-address-lookup
+@kindex show force-internal-tls-address-lookup
+@cindex internal TLS lookup
+Turns on or off forced use of @value{GDBN}-internal TLS (Thread Local
+Storage) address lookup code.  Use @code{on} to enable and @code{0} to
+disable.
+
+When disabled, @value{GDBN} will attempt to use a helper
+@code{libthread_db} library if possible, but will fall back to use of
+its own internal TLS address lookup mechanisms if necessary.
+
+When enabled, @value{GDBN} will only use the @value{GDBN}'s internal
+TLS address lookup mechanisms, if they exist.
+
+This command is only available on targets for which internal TLS
+address lookup support exists.
+
 @kindex set debug libthread-db
 @kindex show debug libthread-db
 @cindex debugging @code{libthread_db}
-- 
2.46.2


  parent reply	other threads:[~2024-10-10  2:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  2:16 [PATCH 00/11] GDB-internal TLS support for Linux targets Kevin Buettner
2024-10-10  2:16 ` [PATCH 01/11] Don't attempt to find TLS address when target has no registers Kevin Buettner
2024-10-10  2:16 ` [PATCH 02/11] Allow TLS access to work in gdb.server/no-thread-db.exp Kevin Buettner
2024-10-10  2:16 ` [PATCH 03/11] Track and fetch TLS module ids for MUSL and GLIBC Kevin Buettner
2024-10-10  2:16 ` [PATCH 04/11] Implement internal TLS address lookup for Linux targets Kevin Buettner
2024-10-10  2:16 ` [PATCH 05/11] Internal TLS support for aarch64, x86_64, riscv, ppc64, and s390x Kevin Buettner
2024-10-11  8:12   ` Luis Machado
2024-10-11 19:48     ` Kevin Buettner
2024-10-10  2:16 ` [PATCH 06/11] Internal, but disabled, TLS support for i386 Kevin Buettner
2024-10-10  2:16 ` [PATCH 07/11] Delete disabled i386 internal TLS support Kevin Buettner
2024-10-10  2:16 ` [PATCH 08/11] New test - gdb.base/tls-nothreads.exp Kevin Buettner
2024-10-10  2:16 ` [PATCH 09/11] New test - gdb.base/tls-multiobj.exp Kevin Buettner
2024-10-10  2:16 ` [PATCH 10/11] New test - gdb.base/tls-dlobj.exp Kevin Buettner
2024-10-10  2:16 ` Kevin Buettner [this message]
2024-10-10  6:01   ` [PATCH 11/11] Add TLS NEWS entry and document 'set force-internal-tls-address-lookup' command Eli Zaretskii
2024-10-10 23:27     ` Kevin Buettner
2024-10-11  5:42       ` Eli Zaretskii
2024-10-11 16:15         ` Kevin Buettner

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=20241010022552.47637-12-kevinb@redhat.com \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@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