This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFC] 09/10 Add "continue --all"

From: Daniel Jacobowitz <drow at false dot org>
To: Michael Snyder <msnyder at specifix dot com>
Cc: Pedro Alves <pedro at codesourcery dot com>, gdb-patches at sourceware dot org, Joel Brobecker <brobecker at adacore dot com>, Eli Zaretskii <eliz at gnu dot org>
Date: Mon, 19 May 2008 14:25:37 -0400
Subject: Re: [RFC] 09/10 Add "continue --all"
References: <200805061649.50105.pedro@codesourcery.com> <20080509122003.GA24290@caradoc.them.org> <20080511160001.GI28890@adacore.com> <200805191620.23279.pedro@codesourcery.com> <1211221182.3601.9.camel@localhost.localdomain>

On Mon, May 19, 2008 at 11:19:42AM -0700, Michael Snyder wrote:
> What about "continue /all"?  More in keeping with the
> argument syntax of existing gdb commands (print, examine...)

So far there are only single letter specifiers, and they're all output
formats (print/x, disassemble/m).  Adding multi-letter ones
would be pretty confusing, IMO.

If we want functionality arguments, especially multi-letter ones, I
have a small preference for --all.

Well, that's my two cents.

-- 
Daniel Jacobowitz
CodeSourcery

Follow-Ups:
- Re: [RFC] 09/10 Add "continue --all"
  - From: Andreas Schwab

References:
- [RFC] 09/10 Add "continue --all"
  - From: Pedro Alves
- Re: [RFC] 09/10 Add "continue --all"
  - From: Daniel Jacobowitz
- Re: [RFC] 09/10 Add "continue --all"
  - From: Joel Brobecker
- Re: [RFC] 09/10 Add "continue --all"
  - From: Pedro Alves
- Re: [RFC] 09/10 Add "continue --all"
  - From: Michael Snyder

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]