From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Brian Heilig <bheilig@etinternational.com>
Subject: Re: Porting gdb to Cyclops64
Date: Mon, 02 Aug 2010 13:35:00 -0000 [thread overview]
Message-ID: <201008021435.16106.pedro@codesourcery.com> (raw)
In-Reply-To: <1280755494.1560.47.camel@random>
On Monday 02 August 2010 14:24:54, Brian Heilig wrote:
> On Sat, 2010-07-31 at 00:17 +0100, Pedro Alves wrote:
> > Not sure what you mean --- the user would still have to resume each
> > thread individually. But yes, in non-stop mode, your target should
> > let the other threads that hadn't hit any breakpoint continue running
> > free.
>
> My understanding is that in non-stop mode I can "continue all", whereas
> in stop mode I can only continue the current thread. This would mean
> that, in stop mode, each thread would have to be continued in
> succession.
In all-stop mode, what's resumed depends on the "set scheduler-locking"
setting. By default, gdb tells the target to continue all
threads (vCont;c).
--
Pedro Alves
next prev parent reply other threads:[~2010-08-02 13:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 17:13 Brian Heilig
2010-07-30 17:26 ` Michael Snyder
2010-07-30 18:53 ` Brian Heilig
2010-07-30 18:57 ` Michael Snyder
2010-07-30 20:28 ` Brian Heilig
2010-07-30 22:54 ` Michael Snyder
2010-07-30 23:18 ` Pedro Alves
2010-08-02 13:25 ` Brian Heilig
2010-08-02 13:35 ` Pedro Alves [this message]
2010-08-03 16:52 ` Brian Heilig
2010-08-05 13:56 ` Brian Heilig
2010-08-05 14:19 ` Pedro Alves
2010-08-06 18:39 ` Problems with non-stop - " Brian Heilig
2010-08-30 19:44 ` Cyclops64 Multi-Process Brian Heilig
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=201008021435.16106.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=bheilig@etinternational.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).