From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7267 invoked by alias); 25 Jun 2010 18:25:19 -0000 Received: (qmail 7252 invoked by uid 22791); 25 Jun 2010 18:25:18 -0000 X-SWARE-Spam-Status: No, hits=-5.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD 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; Fri, 25 Jun 2010 18:25:14 +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.13.8/8.13.8) with ESMTP id o5PIPC0L007997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 25 Jun 2010 14:25:12 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o5PIPCLr021040; Fri, 25 Jun 2010 14:25:12 -0400 Received: from opsy.redhat.com (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 o5PIPB7N017576; Fri, 25 Jun 2010 14:25:11 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 19F073792DB; Fri, 25 Jun 2010 12:25:11 -0600 (MDT) From: Tom Tromey To: Phil Muldoon Cc: gdb-patches@sourceware.org Subject: Re: [patch] PR python/11407 References: <4C23426F.4020502@redhat.com> <4C23D5CB.5040702@redhat.com> Reply-To: tromey@redhat.com Date: Fri, 25 Jun 2010 18:25:00 -0000 In-Reply-To: <4C23D5CB.5040702@redhat.com> (Phil Muldoon's message of "Thu, 24 Jun 2010 23:01:47 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.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: 2010-06/txt/msg00591.txt.bz2 >>>>> "Phil" == Phil Muldoon writes: Phil> I'm not sure what to do in this case. There seems to be no direct Phil> equivalent of converting an exception to error output on a stream in MI Phil> (or any cases of TRY ... exception handlers). There are many cases of Phil> MI raising an error() though, so I thought it appropriate in our case Phil> to raise a warning() instead. Because of the peculiarities of the MI Phil> cases I just report a warning generically and move on. This is not Phil> totally ideal, but it does allow the error/warning preamble followed Phil> by the actual locals information. I'm not convinced a warning is the best thing. Why not catch the exception and print the text of it as the variable's value? Something like I think this will work ok with existing front ends. Tom