From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: RFC: Access TLS symbols without DWARF debuginfo
Date: Wed, 18 Oct 2006 04:27:00 -0000 [thread overview]
Message-ID: <uodsaqmda.fsf@gnu.org> (raw)
In-Reply-To: <20061017210311.GB12643@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 17 Oct 2006 17:03:11 -0400)
> Date: Tue, 17 Oct 2006 17:03:11 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
>
> On Tue, Oct 10, 2006 at 06:25:12AM +0200, Eli Zaretskii wrote:
> > > Date: Mon, 9 Oct 2006 23:22:26 -0400
> > > From: Daniel Jacobowitz <drow@false.org>
> > > Cc: Eli Zaretskii <eliz@gnu.org>
> > >
> > > Eli, this patch added support for printing thread local (__thread)
> > > variables in files without debugging information, on platforms where we
> > > could already do it with debugging information. I'm undecided on
> > > whether that's NEWS-worthy. What do you think?
> >
> > I think we should mention it in NEWS.
>
> Is this OK?
Shouldn't we mention thread-local variables explicitly, even if only
as an "e.g."?
Otherwise, fine with me. Thanks.
prev parent reply other threads:[~2006-10-18 4:27 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
2006-10-18 4:27 ` 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=uodsaqmda.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.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