From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-67961-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 21002 invoked by alias); 23 Oct 2009 15:36:13 -0000
Received: (qmail 20992 invoked by uid 22791); 23 Oct 2009 15:36:13 -0000
X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from smtp-outbound-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 23 Oct 2009 15:36:09 +0000
Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) 	by smtp-outbound-2.vmware.com (Postfix) with ESMTP id D4C1553054; 	Fri, 23 Oct 2009 08:36:05 -0700 (PDT)
Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) 	by mailhost4.vmware.com (Postfix) with ESMTP id C937FC9B82; 	Fri, 23 Oct 2009 08:36:05 -0700 (PDT)
Message-ID: <4AE1CBCC.3010706@vmware.com>
Date: Fri, 23 Oct 2009 15:36:00 -0000
From: Michael Snyder <msnyder@vmware.com>
User-Agent: Thunderbird 1.5.0.12 (X11/20080411)
MIME-Version: 1.0
To: Pedro Alves <pedro@codesourcery.com>
CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] Error reporting during insert_breakpoints
References: <4A26E026.2000705@vmware.com> <200906032246.44508.pedro@codesourcery.com>
In-Reply-To: <200906032246.44508.pedro@codesourcery.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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-10/txt/msg00584.txt.bz2

Pedro Alves wrote:
> On Wednesday 03 June 2009 21:42:14, Michael Snyder wrote:
>> Two small changes
>>
>> 1) If insert_breakpoints fails during stepping, "keep_going()"
>> contains a TRY_CATCH block, but does not print the exception error.
>> If the same thing happens during continue, "catch_errors" reports it.
> 
> Yes, please.  This silent stop bites me often, when longjmp-resume
> breakpoints fail to insert due to glibc pointer mangling...

Fell through the cracks, checking in now.