From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 101876 invoked by alias); 17 Aug 2018 15:38:46 -0000 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 Received: (qmail 101864 invoked by uid 89); 17 Aug 2018 15:38:46 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:850, maintains, cryptic, Apart X-HELO: mx1.redhat.com Received: from mx3-rdu2.redhat.com (HELO mx1.redhat.com) (66.187.233.73) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 17 Aug 2018 15:38:45 +0000 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C4F9A26364; Fri, 17 Aug 2018 15:38:43 +0000 (UTC) Received: from blade.nx (ovpn-117-165.ams2.redhat.com [10.36.117.165]) by smtp.corp.redhat.com (Postfix) with ESMTP id 7C4442156712; Fri, 17 Aug 2018 15:38:43 +0000 (UTC) Received: by blade.nx (Postfix, from userid 1000) id CF9C680AFCC4; Fri, 17 Aug 2018 16:38:42 +0100 (BST) Date: Fri, 17 Aug 2018 15:38:00 -0000 From: Gary Benson To: Pedro Alves Cc: Tom Tromey , gdb-patches@sourceware.org Subject: Re: [PATCH] Indicate batch mode failures by exiting with nonzero status Message-ID: <20180817153841.GB25958@blade.nx> References: <1534425783-11599-1-git-send-email-gbenson@redhat.com> <87r2ix98pk.fsf@tromey.com> <20180817105923.GA32726@blade.nx> <77a79412-a15c-b69a-fd11-404913e802e4@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <77a79412-a15c-b69a-fd11-404913e802e4@redhat.com> X-IsSubscribed: yes X-SW-Source: 2018-08/txt/msg00425.txt.bz2 Pedro Alves wrote: > If we went that route, I'd think that could be a separate orthogonal > option. I.e., a "stop/continue processing commands on first error" > option. That could be used even without -batch. > > That would be something in the same spirit of the new > "thread apply" / "frame apply" flags: > > FLAG arguments are -q (quiet), -c (continue), -s (silent). I think, if we're going to add the behaviour that GDB should stop on error, then that behaviour should be the default, at least for batch mode. Stopping at the first error is what most languages do isn't it? Apart from shell scripts :) Having to have an option to enable the intuitive behaviour (what *I* think is intuitive anyway) just maintains GDB's reputation as cryptic and hard to use. Cheers, Gary