From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26887 invoked by alias); 1 Nov 2012 20:30:50 -0000 Received: (qmail 26872 invoked by uid 22791); 1 Nov 2012 20:30:49 -0000 X-SWARE-Spam-Status: No, hits=-5.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-oa0-f41.google.com (HELO mail-oa0-f41.google.com) (209.85.219.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 01 Nov 2012 20:30:44 +0000 Received: by mail-oa0-f41.google.com with SMTP id k14so3350046oag.0 for ; Thu, 01 Nov 2012 13:30:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-system-of-record:x-gm-message-state; bh=qOkW9P1KHRfjC2uAw/vC8WZ6MoFeDWyWO1p71mCsLlc=; b=BaLABrEtaTyRMQi+6n2Dh44mZpQRIWIBFzynBO4cPYcw2IoouFDfeJmjSCvsIEff/B OodAeANAUuFjNHo2F7SUeqLQsZfbzplttmi88YVgBJOZKwPFiT7TH6JKg2vqhkDazjIy hbJrxFW8JlLZjbDXmNXpYkxOijJFKBM8JNyVW8zpr8AywHd1/mVbpdTbDiwUxPjE+W12 v1mB5ofa/pLMe2Yg4P0isR/vPUD3lEdmjKt+4KnQgLUBHcrEaaPG10j7c6tspAhOGI/G O/1Irq1zyTaAjB6EbWg58bbrI/9kk2WI43nKiVYVbEjXNmBnMQC+g0tgakcAnePdl8vP LJhQ== MIME-Version: 1.0 Received: by 10.60.36.73 with SMTP id o9mr1113358oej.23.1351801843626; Thu, 01 Nov 2012 13:30:43 -0700 (PDT) Received: by 10.76.71.201 with HTTP; Thu, 1 Nov 2012 13:30:43 -0700 (PDT) In-Reply-To: <87390vyhxq.fsf@fleche.redhat.com> References: <7D0928B9A8397D4B9E2F9E5FFFB8D860027BED37@G6W2492.americas.hpqcorp.net> <509010B5.6050309@redhat.com> <87390vyhxq.fsf@fleche.redhat.com> Date: Thu, 01 Nov 2012 20:30:00 -0000 Message-ID: Subject: Re: working around batch mode command errors From: Doug Evans To: Tom Tromey Cc: Pedro Alves , "Maucci, Cyrille" , "gdb@sourceware.org" Content-Type: text/plain; charset=ISO-8859-1 X-System-Of-Record: true X-Gm-Message-State: ALoCoQkk1c9CkuoMAwJivPxmJW0NVc07yFRUEUDnWpEQnlEcuRLVnoyi8cj1zovtVFQux3LQNy0PiA8lVLT7+C7GqF/mw+jeHnydgVYohIcP0UHaJ2I8vJkfVSKMDRNXP5DCwnDa3ntAeilTLEbOG6AApVFpBz63lTWn2oUXabcFWwqf5Utxd/1EXo/8L2/f5+HYp2sxwOXG X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-11/txt/msg00000.txt.bz2 On Tue, Oct 30, 2012 at 10:43 AM, Tom Tromey wrote: >>>>>> "Pedro" == Pedro Alves writes: > > Pedro> There's no try/catch mechanism in the CLI unfortunately, but I > Pedro> think you could come up with one in python gdb. ISTR Tromey had > Pedro> a python command wrapper that swallows CLI errors? > > Yeah, http://www.sourceware.org/ml/gdb/2010-06/msg00100.html > > There's a more full-blown try/catch implementation in bugzilla. > That one isn't in Python. I don't know why it never went in. > > This seems to be a frequently requested feature. > > Tom I went looking for the bugzilla entry but couldn't find it. try: gdb.execute (...) except: pass is just too much to type. :-)