From: Sandra Loosemore <sandra@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: Cannot execute this command without a live selected thread.
Date: Fri, 24 Oct 2014 19:02:00 -0000 [thread overview]
Message-ID: <544AA205.7020005@codesourcery.com> (raw)
In-Reply-To: <544A8F15.9000906@redhat.com>
On 10/24/2014 11:40 AM, Pedro Alves wrote:
> On 10/24/2014 06:23 PM, Pedro Alves wrote:
>>
>> We may be able add a workaround for this. :-/ Just in case,
>> can you confirm that the current thread's ptid (inferior_ptid)
>> is magic_null_ptid?
>
> Please give this a try.
The patch works fine for hand-testing of a hello world program (can load
and run it and stop at breakpoint on main, at least). I've kicked off a
full set of tests.
-Sandra
next prev parent reply other threads:[~2014-10-24 19:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 15:55 Sandra Loosemore
2014-10-24 16:07 ` Pedro Alves
2014-10-24 17:08 ` Sandra Loosemore
2014-10-24 17:23 ` Pedro Alves
2014-10-24 17:40 ` Pedro Alves
2014-10-24 19:02 ` Sandra Loosemore [this message]
2014-10-24 19:19 ` Doug Evans
2014-10-24 19:40 ` Pedro Alves
2014-10-24 20:02 ` Doug Evans
2014-10-24 20:20 ` Pedro Alves
2014-10-24 20:38 ` Doug Evans
2014-10-24 20:52 ` Remove libthread_db -> remove thread_stratum? [was Re: Cannot execute this command without a live selected thread.] Doug Evans
2014-10-24 22:07 ` Cannot execute this command without a live selected thread Pedro Alves
2014-10-27 19:53 ` Sandra Loosemore
2014-10-28 12:10 ` [pushed] Workaround remote targets that report an empty list to qfThreadInfo (Re: Cannot execute this command without a live selected thread.) Pedro Alves
2014-10-29 19:16 ` Doug Evans
2014-10-24 17:57 ` Cannot execute this command without a live selected thread Sandra Loosemore
2014-10-24 18:15 ` 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=544AA205.7020005@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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