From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7613 invoked by alias); 6 Jul 2008 17:28:00 -0000 Received: (qmail 7604 invoked by uid 22791); 6 Jul 2008 17:28:00 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 06 Jul 2008 17:27:42 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m66HRZl3023924; Sun, 6 Jul 2008 13:27:35 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m66HRZYJ018369; Sun, 6 Jul 2008 13:27:35 -0400 Received: from opsy.redhat.com (vpn-10-25.bos.redhat.com [10.16.10.25]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m66HRY2c024666; Sun, 6 Jul 2008 13:27:34 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id A4AE037817E; Sun, 6 Jul 2008 11:27:33 -0600 (MDT) To: thiagoju@linux.ibm.com Cc: Daniel Jacobowitz , Thiago Jung Bauermann , gdb-patches@sourceware.org Subject: Re: [RFC][patch 1/9] initial Python support References: <20080429155212.444237503@br.ibm.com> <20080429155304.288626880@br.ibm.com> <20080528205921.GA2969@caradoc.them.org> <20080615181833.uxmo25mg0kko40kw@imap.linux.ibm.com> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Sun, 06 Jul 2008 17:28:00 -0000 In-Reply-To: (Tom Tromey's message of "Mon\, 23 Jun 2008 11\:25\:30 -0600") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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-07/txt/msg00078.txt.bz2 >>>>> "Tom" == Tom Tromey writes: >>> > + if (PyErr_Occurred ()) >>> > + { >>> > + PyErr_Print (); >>> > + error ("error while executing Python code"); >>> > + } >>> > +} Thiago> This is stillpending, I think. FYI -- I fixed this today. I added a new 'maint set python-stack' variable that controls whether Python stack traces are printed. By default they are. I changed all the new code to use a new gdbpy_print_stack which checks this variable. Finally, I set things up so that gdb overrides Python's sys.stdout and sys.stderr to print things using printf_filtered. Tom