This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Single stepping and threads
- From: Michael Snyder <Michael dot Snyder at palmsource dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb at sourceware dot org
- Date: Fri, 01 Dec 2006 14:28:53 -0800
- Subject: Re: Single stepping and threads
- References: <20061129052942.GA16029@nevyn.them.org> <20061129055915.GM9968@adacore.com> <20061129132535.GA28834@nevyn.them.org> <20061129163844.GN9968@adacore.com> <1164929776.14460.36.camel@localhost.localdomain> <20061130235515.GI3491@adacore.com>
On Thu, 2006-11-30 at 15:55 -0800, Joel Brobecker wrote:
> > Default on would be a disaster -- most threaded programs would
> > not behave even remotely the same under the debugger as they would
> > solo.
> >
> > In fact, many would deadlock almost immediately.
>
> Something just occured to me that was clear but maybe isn't. Is the
> scheduling affected when you do a "continue"? I assumed that, if you
> do a "run" or "continue", the actual scheduling policy is irrelevant,
> and all threads are resumed.
"Schedlock step" does not affect the continue behavior,
but "schedlock on" does. With "on", no other thread can
execute, period.