From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28635 invoked by alias); 9 Nov 2011 20:25:11 -0000 Received: (qmail 28605 invoked by uid 22791); 9 Nov 2011 20:25:07 -0000 X-SWARE-Spam-Status: No, hits=-7.1 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, 09 Nov 2011 20:24:53 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pA9KOqPY029063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 Nov 2011 15:24:53 -0500 Received: from localhost.localdomain (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id pA9KOpHJ025929; Wed, 9 Nov 2011 15:24:52 -0500 From: Phil Muldoon To: Kevin Pouget Cc: gdb-patches@sourceware.org Subject: Re: [python] [patch] PR python/13329 References: Reply-to: pmuldoon@redhat.com X-URL: http://www.redhat.com Date: Wed, 09 Nov 2011 20:25:00 -0000 In-Reply-To: (Kevin Pouget's message of "Wed, 9 Nov 2011 16:48:58 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes 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-11/txt/msg00264.txt.bz2 Kevin Pouget writes: > Thanks Phil, that's exactly what I was looking for :) > > just a remark, > > + fprintf_filtered (gdb_stderr, > + _("Error occurred computing Python error" \ > + "message.\n")); > > this error message sounds strange to me, is it correct? Yes, this happens when we cannot get the exception message, but an exception has been set. I don't ever expect this error to actually be seen, but it can happen depending on the state of the interpreter. Looking at it again, I do see I did miss a space between 'error' and 'message' though! Cheers, Phil