From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-63001-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 4399 invoked by alias); 16 Apr 2009 22:09:22 -0000
Received: (qmail 4390 invoked by uid 22791); 16 Apr 2009 22:09:20 -0000
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 	tests=AWL,BAYES_00,J_CHICKENPOX_25,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 16 Apr 2009 22:09:15 +0000
Received: (qmail 16899 invoked from network); 16 Apr 2009 22:09:12 -0000
Received: from unknown (HELO orlando) (pedro@127.0.0.2)   by mail.codesourcery.com with ESMTPA; 16 Apr 2009 22:09:12 -0000
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] print error message if (auto) disassembly failed
Date: Thu, 16 Apr 2009 22:09:00 -0000
User-Agent: KMail/1.9.10
Cc: Joel Brobecker <brobecker@adacore.com>,  Eli Zaretskii <eliz@gnu.org>
References: <20090416173918.GP7557@adacore.com> <83vdp4jn6j.fsf@gnu.org> <20090416215426.GL7585@adacore.com>
In-Reply-To: <20090416215426.GL7585@adacore.com>
MIME-Version: 1.0
Content-Type: text/plain;   charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200904162309.20373.pedro@codesourcery.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-04/txt/msg00395.txt.bz2

On Thursday 16 April 2009 22:54:26, Joel Brobecker wrote:
> > OK, but your suggested message text is too long, I think.  Something
> > shorter, like "(address unreadable)" is better, IMO.
> 
> I just printing the error message that has been "thrown". I don't see
> any way of printing what you want without parsing that error message.
> Do you see any?

I haven't been following the thread, so sorry if this overshoots
too far away, but, anyway, notice that there's now a MEMORY_ERROR error
class in exceptions.h.  If you have access to the error exception object,
you can check on ex.error.  See breakpoint.c:fetch_watchpoint_value for
a MEMORY_ERROR filtering usage.

-- 
Pedro Alves