[non-stop] 00/10 non-stop mode

[Pedro Alves]

A Wednesday 18 June 2008 23:21:16, Nick Roberts wrote:
>  > > In that case I'm not really sure what you mean by core - non-stop mode
>  > > includes changes to linux-nat.c, so presumably that is linux only.
>  >
>  > I don't follow where you're getting at.  Async mode requires
>  > target support, but of course there's also code in the core of
>  > GDB to support it.  Non-stop mode requires target support, builds
>  > on top of the async mode, and of course needs core support too.
>
> I mean, for consistency, shouldn't it be:
>
> maint set non-stop 1
>

Ah, I see where you're confused.   Enabling async support or not, is
something that ideally we shouldn't need to give the user
an option for.  Therefore, it's a maintainer command, that we'll
use until the reasons we have it go away.

Selecting non-stop or all-stop modes, is something the user will
want to do (even if all-stop mode gets to be implemented on top of
non-stop in the future), as both modes are useful.

> since this option presumably also only works for linux (and remote?).

Just linux currently.  remote's in the queue.

-- 
Pedro Alves