From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15246 invoked by alias); 9 Aug 2010 19:41:18 -0000 Received: (qmail 15234 invoked by uid 22791); 9 Aug 2010 19:41:16 -0000 X-SWARE-Spam-Status: No, hits=-5.5 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; Mon, 09 Aug 2010 19:41:11 +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 o79Jf4T2000710 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Aug 2010 15:41:04 -0400 Received: from Phil-THINK.home (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 o79Jf3ZX013964; Mon, 9 Aug 2010 15:41:03 -0400 Message-ID: <4C6059CE.2050300@redhat.com> Date: Mon, 09 Aug 2010 19:41:00 -0000 From: Phil Muldoon User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100720 Fedora/3.1.1-1.fc13 Thunderbird/3.1.1 MIME-Version: 1.0 To: tromey@redhat.com CC: gdb-patches@sourceware.org, vladimir@codesourcery.com Subject: Re: [patch] PR python/11407 References: <4C23426F.4020502@redhat.com> <4C23D5CB.5040702@redhat.com> <4C251D93.6020909@redhat.com> <4C34B319.2030901@redhat.com> In-Reply-To: <4C34B319.2030901@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 2010-08/txt/msg00110.txt.bz2 On 07/07/10 18:02, Phil Muldoon wrote: > On 25/06/10 22:20, Phil Muldoon wrote: >> On 06/25/2010 07:25 PM, Tom Tromey wrote: >>>>>>>> "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. >> >> Here is a patch that does that. >> >> What do you think? >> >> Cheers, >> >> Phil >> > > Tom >> I am curious to hear what Volodya wants. > > > Adding Vladimir Prus to the CC list. > Ping