From: Daniel Jacobowitz <drow@false.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Access TLS symbols without DWARF debuginfo
Date: Wed, 18 Oct 2006 15:29:00 -0000 [thread overview]
Message-ID: <20061018152933.GA10436@nevyn.them.org> (raw)
In-Reply-To: <uodsaqmda.fsf@gnu.org> <20061017220313.GA809@host0.dyn.jankratochvil.net>
On Wed, Oct 18, 2006 at 12:03:13AM +0200, Jan Kratochvil wrote:
> Please note the TLS support is still not complete:
>
> * Support for GNU/Linux Thread Local Storage (TLS) no longer requires
> symbolic debug information (e.g. DWARF-2). It requires the inferior process to
> use threads (to be linked -lpthread).
True - but this is NEWS, not a list of limitations, so I'm going to
omit that.
On Wed, Oct 18, 2006 at 06:27:45AM +0200, Eli Zaretskii wrote:
> Shouldn't we mention thread-local variables explicitly, even if only
> as an "e.g."?
>
> Otherwise, fine with me. Thanks.
Good point. I've checked in this version.
--
Daniel Jacobowitz
CodeSourcery
2006-10-17 Daniel Jacobowitz <dan@codesourcery.com>
* NEWS: Mention support for TLS without debugging information.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.197
diff -u -p -r1.197 NEWS
--- NEWS 16 Aug 2006 20:33:23 -0000 1.197
+++ NEWS 18 Oct 2006 15:28:34 -0000
@@ -14,6 +14,9 @@ supported.
* The "set trust-readonly-sections" command works again. This command was
broken in GDB 6.3, 6.4, and 6.5.
+* Support for GNU/Linux Thread Local Storage (TLS, per-thread variables) no
+longer requires symbolic debug information (e.g. DWARF-2).
+
* New commands
set substitute-path
next prev parent reply other threads:[~2006-10-18 15:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 13:43 RFC: Ignore TLS symbols for non-TLS programs Jan Kratochvil
2006-08-25 16:43 ` Daniel Jacobowitz
2006-08-26 11:56 ` Daniel Jacobowitz
2006-08-25 13:48 ` RFC: Access TLS symbols without DWARF debuginfo Jan Kratochvil
2006-08-25 20:02 ` Daniel Jacobowitz
2006-08-28 18:27 ` RFC: Access TLS symbols without DWARF debuginfo v2 Jan Kratochvil
2006-08-28 21:02 ` Jim Blandy
2006-08-29 11:41 ` Daniel Jacobowitz
2006-10-09 20:20 ` Daniel Jacobowitz
2006-10-10 3:22 ` RFC: Access TLS symbols without DWARF debuginfo Daniel Jacobowitz
2006-10-10 4:25 ` Eli Zaretskii
2006-10-17 21:03 ` Daniel Jacobowitz
2006-10-17 22:03 ` Jan Kratochvil
2006-10-18 15:29 ` Daniel Jacobowitz [this message]
2006-10-18 4:27 ` Eli Zaretskii
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=20061018152933.GA10436@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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