This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [MI non-stop 06/11, RFA/RFC] Report non-stop availability, and allow to enable everything with one command.
- From: Vladimir Prus <vladimir at codesourcery dot com>
- To: Pedro Alves <pedro at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Tue, 12 Aug 2008 16:46:38 +0400
- Subject: Re: [MI non-stop 06/11, RFA/RFC] Report non-stop availability, and allow to enable everything with one command.
- References: <200806282054.03092.vladimir@codesourcery.com> <200808121009.11540.vladimir@codesourcery.com> <20080812120835.GA29188@caradoc.them.org>
On Tuesday 12 August 2008 16:08:35 Daniel Jacobowitz wrote:
> On Tue, Aug 12, 2008 at 10:09:11AM +0400, Vladimir Prus wrote:
> > My motivation was that the most intuitive model is that of
> > immediate application of non-stop flag, with error produced
> > immediately. This is hard to implement.
> >
> > Next most intuitive model is "I prefer non-stop mode", which is
> > what I propose.
>
> Actually I think this is very unintuitive. You'll have to know
> whether you get non-stop or not because commands act very differently
> between all-stop and non-stop. Scripts written for the one won't work
> with the other, for example.
Yes, you have to know whether you get non-stop or not -- does this contradict
to anything I've said?
- Volodya