Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [MI non-stop 06/11, RFA/RFC] Report non-stop availability, and 	allow to enable everything with one command.
Date: Tue, 12 Aug 2008 12:09:00 -0000	[thread overview]
Message-ID: <20080812120835.GA29188@caradoc.them.org> (raw)
In-Reply-To: <200808121009.11540.vladimir@codesourcery.com>

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.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-08-12 12:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-28 16:57 Vladimir Prus
2008-07-11 13:34 ` Pedro Alves
2008-07-23  7:48   ` Vladimir Prus
2008-07-28 17:58     ` Pedro Alves
2008-08-04 12:59       ` Vladimir Prus
2008-08-05 16:31         ` Pedro Alves
2008-08-05 18:28           ` Daniel Jacobowitz
2008-08-05 19:09             ` Pedro Alves
2008-08-12  6:10               ` Vladimir Prus
2008-08-12 12:09                 ` Daniel Jacobowitz [this message]
2008-08-12 12:47                   ` Vladimir Prus
2008-08-12 13:01                     ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080812120835.GA29188@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=vladimir@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox