From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] PR python/20190 - compute TLS symbol without a frame
Date: Fri, 22 Jul 2016 11:18:00 -0000 [thread overview]
Message-ID: <e16d960e-650b-599d-fd23-d836b0dd0353@redhat.com> (raw)
In-Reply-To: <87oa6lt3pm.fsf@tromey.com>
On 06/28/2016 10:15 PM, Tom Tromey wrote:
>>>>>> "Yao" == Yao Qi <qiyaoltc@gmail.com> writes:
>
> Yao> I don't understand why your original attempt fixing PR11803
> Yao> (https://sourceware.org/ml/gdb-patches/2010-07/msg00374.html)
> Yao> doesn't work here.
>
> The difference is in what happens when you try to refer to a __thread
> variable without an inferior. I think this was pointed out in one of
> the follow-ups.
>
> With the original patch, the failure mode looks like:
>
> (gdb) print a_thread_local
> Cannot find thread-local storage for process 0, executable file /home/tromey/gdb/build/gdb/testsuite/outputs/gdb.threads/tls/tls:
> Cannot find thread-local variables on this target
>
> With the current patch the result is nicer:
>
> (gdb) print a_thread_local
> Cannnot read `a_thread_local' without registers
Is this / should this be tested somewhere?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-07-22 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 21:16 Tom Tromey
2016-06-28 14:11 ` Yao Qi
2016-06-28 21:15 ` Tom Tromey
2016-07-22 11:18 ` Pedro Alves [this message]
2016-07-22 11:14 ` Pedro Alves
2016-07-24 16:53 ` Tom Tromey
2016-07-25 16:00 ` Pedro Alves
2016-07-26 16:47 ` Tom Tromey
2016-07-26 17:28 ` Pedro Alves
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=e16d960e-650b-599d-fd23-d836b0dd0353@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
--cc=tom@tromey.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).