From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22386 invoked by alias); 24 Nov 2004 04:02:43 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 22341 invoked from network); 24 Nov 2004 04:02:37 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 24 Nov 2004 04:02:37 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1CWoMX-0006J1-0z; Tue, 23 Nov 2004 23:02:37 -0500 Date: Wed, 24 Nov 2004 04:47:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: gdb@sources.redhat.com Subject: Re: Breaking exceptions before stack unwind Message-ID: <20041124040237.GA24202@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , gdb@sources.redhat.com References: <419A5E71.8030304@stankevitz.com> <20041117230803.GC22472@nevyn.them.org> <01c4d157$Blat.v2.2.2$96e70920@zahav.net.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01c4d157$Blat.v2.2.2$96e70920@zahav.net.il> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-11/txt/msg00234.txt.bz2 On Tue, Nov 23, 2004 at 02:24:57PM +0200, Eli Zaretskii wrote: > > Date: Wed, 17 Nov 2004 18:08:03 -0500 > > From: Daniel Jacobowitz > > Cc: gdb@sources.redhat.com > > > > On Tue, Nov 16, 2004 at 12:09:21PM -0800, Chris Stankevitz wrote: > > > > > > According to the GDB documentation, you can tell gdb to break on all > > > exceptions with this command: > > > break __raise_exception > > > > > > This does not work for me (not defined). Others suggested this: > > > break __cp_push_exception > > > > > > That doesn't work for me either (not defined). > > > > > > I have two questions: > > > > > > 1. Why don't either of those two options work for me? > > > > Obsolete documentation. > > The obsolete advice is still in the manual. What should we do to > un-obsolete it? Are there any alternative library functions to try? > Should we perhaps delete the whole paragraph, and instead tell users > how to work around problems with shared library loading with the trick > you cited later in this thread ("set stop-on-solib-events 1; run")? The workaround is only necessary because he was using GDB 5.3 - Jeff's pending breakpoints implementation is even better. Yes, the documentation does need to be fixed. I can't do it right now, but the right thing to do is to document 'catch catch' and 'catch throw'. They're pretty limited right now, but they do work. -- Daniel Jacobowitz