From: Yao Qi <yao@codesourcery.com>
To: <jeremy.bennett@embecosm.com>
Cc: <gdb@sourceware.org>
Subject: Re: Why does "target remote" to a non-stop target stop one thread
Date: Fri, 28 Jun 2013 08:15:00 -0000 [thread overview]
Message-ID: <51CD45EE.6030501@codesourcery.com> (raw)
In-Reply-To: <51CCA2AB.1000008@embecosm.com>
On 06/28/2013 04:38 AM, Jeremy Bennett wrote:
> hen I connect to the target, even in non-stop mode, it insists on
> stopping one thread. The comment in notice_new_inferior () is:
>
>> > /* We're going to install breakpoints, and poke at memory,
>> > ensure that the inferior is stopped for a moment while we do
>> > that. */
> My question is, why we need to stop any thread. Surely the whole point
> of non-stop mode is that we don't generally want to stop any threads if
> it can be avoided.
Hi Jeremy,
AFAIK, "non-stop" means when GDB is examining one stopped thread while
other threads are _not stopped_.
See
http://sourceware.org/gdb/onlinedocs/gdb/Non_002dStop-Mode.html#Non_002dStop-Mode
GDB needs the thread stopped because ptrace can't be performed on the
running thread.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-06-28 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 20:38 Jeremy Bennett
2013-06-28 6:22 ` Raphael Zulliger
2013-06-28 8:15 ` Yao Qi [this message]
2013-06-28 13:06 ` Jeremy Bennett
2013-06-28 13:47 ` Luis Machado
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=51CD45EE.6030501@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=jeremy.bennett@embecosm.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