From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26781 invoked by alias); 19 May 2008 18:26:01 -0000 Received: (qmail 26772 invoked by uid 22791); 19 May 2008 18:26:01 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 19 May 2008 18:25:41 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 219FC983FE; Mon, 19 May 2008 18:25:39 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 708B59835A; Mon, 19 May 2008 18:25:38 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JyA3F-0005nJ-5E; Mon, 19 May 2008 14:25:37 -0400 Date: Mon, 19 May 2008 21:55:00 -0000 From: Daniel Jacobowitz To: Michael Snyder Cc: Pedro Alves , gdb-patches@sourceware.org, Joel Brobecker , Eli Zaretskii Subject: Re: [RFC] 09/10 Add "continue --all" Message-ID: <20080519182537.GA21992@caradoc.them.org> Mail-Followup-To: Michael Snyder , Pedro Alves , gdb-patches@sourceware.org, Joel Brobecker , Eli Zaretskii 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1211221182.3601.9.camel@localhost.localdomain> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-05/txt/msg00574.txt.bz2 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