From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18480 invoked by alias); 3 Dec 2012 21:34:38 -0000 Received: (qmail 18091 invoked by uid 22791); 3 Dec 2012 21:34:38 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_SPAMHAUS_DROP,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 03 Dec 2012 21:34:32 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qB3LYVWU027691 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 3 Dec 2012 16:34:31 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id qB3LYUCX012262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 3 Dec 2012 16:34:31 -0500 From: Tom Tromey To: Phil Muldoon Cc: "gdb-patches\@sourceware.org" Subject: Re: [patch][python] 0 of 5 - Frame filters and Wrappers References: <50B8C313.2070404@redhat.com> Date: Mon, 03 Dec 2012 21:34:00 -0000 In-Reply-To: <50B8C313.2070404@redhat.com> (Phil Muldoon's message of "Fri, 30 Nov 2012 14:30:43 +0000") Message-ID: <87k3syvmzd.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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: 2012-12/txt/msg00044.txt.bz2 >>>>> "Phil" == Phil Muldoon writes: Phil> * Frame filters on individual MI commands are turned off with Phil> --no-frame-filters. With the "bt" command, they are turned off with Phil> the raw sub-command (e,g "bt raw"). This is inconsistent at the Phil> moment, and I expect it will be resolved in review. What is it that is inconsistent? Phil> * Python errors when printing? Phil> Right now if there is an error encountered, the frame printing is Phil> aborted and GDB falls back to its own inbuilt printing routines. Phil> This is up for debate, and I hope it sparks a discussion. If the Phil> GDB Python API encounters an error while printing a backtrace, Phil> should it: Phil> - Abandon the whole backtrace, and have the existing GDB code Phil> print it; Phil> - Abandon that frame, and continue on; Considering that frame-printing is lazy, I think it would be weird to try to abandon the whole backtrace and start over. E.g., suppose the error occurred after already displaying the first 5 frames -- starting over would show pretty confusing output. Whether to keep going, I am not sure. When printing an error from a Python printer, it would be very nice for gdb to tell the user how to disable that particular printer. I think this ought to be pretty easy. Tom