Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sandra Loosemore <sandra@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: Cannot execute this command without a live selected thread.
Date: Fri, 24 Oct 2014 16:07:00 -0000	[thread overview]
Message-ID: <544A7930.4040909@redhat.com> (raw)
In-Reply-To: <544A7648.6060102@codesourcery.com>

On 10/24/2014 04:54 PM, Sandra Loosemore wrote:
> Yesterday I refreshed my build tree for testing some further nios2 
> patches, and started seeing a whole lot of this in my test results:
> 
> (gdb) target remote qa8-centos32-cs:10514
> Remote debugging using qa8-centos32-cs:10514
> (gdb) set remote hardware-watchpoint-limit 1
> (gdb) set mem inaccessible-by-default on

This made me suspect of 0fec99e8be72b091618862eafc14e2741f0ff0d5,
though I'm not seeing how that'd end up in the error
in question.

> (gdb) load
> Loading section .text, size 0x844 lma 0x10000000
> Loading section .eh_frame, size 0x4 lma 0x10000844
> Loading section .rodata, size 0x120 lma 0x10000848
> Loading section .data, size 0x428 lma 0x10000968
> Start address 0x10000040, load size 3472
> Transfer rate: 41 KB/sec, 868 bytes/write.
> (gdb) continue
> Continuing.
> Cannot execute this command without a live selected thread.
> (gdb) ERROR: couldn't run to breakpoint
> 

Odd.  A backtrace at (break at "error") and "set debug infrun/remote"
logs would probably be revealing.

> I think the checkout I used for testing the last nios2 patch I submitted 
> was a couple weeks old.  Pedro, I see you checked in a batch of 
> thread-related changes on Oct 15; do you have any clue what's going 
> wrong here?  I can investigate further if it's not obvious, or somebody 
> is not already working on this....

Yeah, I pushed in the whole software single-step rework that day.
Might well be related, given this target uses software single-step.

But it's indeed not obvious and it's the first I hear about it.

Thanks,
Pedro Alves


  reply	other threads:[~2014-10-24 16:07 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 [this message]
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
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=544A7930.4040909@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sandra@codesourcery.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