From: Luis Machado <lgustavo@codesourcery.com>
To: "taylor, david" <david.taylor@emc.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: why does GDB always stop a thread when connecting?
Date: Tue, 05 Apr 2016 17:43:00 -0000 [thread overview]
Message-ID: <5703F931.3020705@codesourcery.com> (raw)
In-Reply-To: <63F1AEE13FAE864586D589C671A6E18B043125@MX203CL03.corp.emc.com>
On 03/28/2016 04:12 PM, taylor, david wrote:
> Why does GDB always stop a thread?
>
> We set non-stop before connecting to our remote target.
> And during the initial back and forth, GDB always tells the
> first thread returned by qfThreadInfo to stop.
>
> Because of this we have arranged for the first thread in the
> list to be a thread that does nothing of consequence -- it is
> imminently stoppable.
>
> But, I would like to understand *WHY* GDB is stopping the thread.
>
> While registers aren't available if the thread is not stopped, that is
> to be expected. Memory can be read and written. Tracepoints and
> breakpoints can be created, enabled, disabled, deleted... Trace
> experiments can be run. Trace frames can be examined...
>
> Why does GDB need a stopped thread when it connects to the
> target?
>
>
Does setting "may-interrupt" to "off" help?
next prev parent reply other threads:[~2016-04-05 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 21:12 taylor, david
2016-04-05 17:43 ` Luis Machado [this message]
2016-04-05 20:52 David Taylor
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=5703F931.3020705@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=david.taylor@emc.com \
--cc=gdb@sourceware.org \
/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