Re: [MI non-stop 06/11, RFA/RFC] Report non-stop availability, and allow to enable everything with one command.

[Daniel Jacobowitz <drow@false.org>]

On Tue, Aug 05, 2008 at 05:30:50PM +0100, Pedro Alves wrote:
> On Monday 04 August 2008 13:58:57, Vladimir Prus wrote:
> > The question is why the connection setup needs to know if we're in
> > non-stop, and why -- which question we discuss below.

You have to know whether you're connecting in non-stop, because if you
connect in all-stop the target might have to stop a running thread
that it would leave running if you connected in non-stop.

I can't follow all the possibilities being juggled in this
conversation.  But why not just set non-stop in advance, regardless of
the target, and then issue an error at run / target remote / wherever
if non-stop is not available?

> We leaves some slack to add new modes like this, which would
> combine (1) and (2):
> 
> set prefered-execution-mode
>  "all-stop"
>     prefer all-stop, but if the target doesn't support it, fine.
>  "non-stop"
>     prefer non-stop, but if the target doesn't support it, fine.
>  "force-all-stop"
>     require all-stop, fail if the target refuses it.
>  "force-non-stop"
>     require all-stop, fail if the target refuses it.

Please don't, the user should know what they get.

-- 
Daniel Jacobowitz
CodeSourcery