From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18985 invoked by alias); 19 Oct 2011 20:56:33 -0000 Received: (qmail 18971 invoked by uid 22791); 19 Oct 2011 20:56:31 -0000 X-SWARE-Spam-Status: No, hits=-7.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,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; Wed, 19 Oct 2011 20:56:16 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9JKuFS4011907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Oct 2011 16:56:15 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p9JKuDvr024631; Wed, 19 Oct 2011 16:56:13 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p9JKuB6S018267; Wed, 19 Oct 2011 16:56:12 -0400 From: Tom Tromey To: Kevin Pouget Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org Subject: Re: [patch] PR python/12438 References: Date: Wed, 19 Oct 2011 20:56:00 -0000 In-Reply-To: (Kevin Pouget's message of "Mon, 17 Oct 2011 14:49:02 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (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: 2011-10/txt/msg00543.txt.bz2 Kevin> I have a question regarding this patch, which was committed at Kevin> the end of June, wouldn't GDB let the user know, one way or an Kevin> other, that there was something wrong happened ? I think gdbpy_print_stack is mostly called in "internal" situations, where printing something will mess up the output. Ordinary commands and such that fail should convert the Python exception to a gdb exception, leading to what you'd expect. I might be misremembering. Concrete examples would help. Kevin> I don't know if Python allows to do it, but i think it would be nice Kevin> to see something like: >> NameError: global name 'comp' is not define Kevin> which is the last line of a python stacktrace I think it could be done. We can always add more values for "maint set python print-stack". Tom