Porting gdb to Cyclops64

Pedro Alves pedro@codesourcery.com
Mon Aug 2 13:35:00 GMT 2010


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



More information about the Gdb mailing list