This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Porting gdb to Cyclops64
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb at sourceware dot org
- Cc: Brian Heilig <bheilig at etinternational dot com>
- Date: Mon, 2 Aug 2010 14:35:15 +0100
- Subject: Re: Porting gdb to Cyclops64
- References: <1280510022.1560.20.camel@random> <201007310017.53475.pedro@codesourcery.com> <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