From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11840 invoked by alias); 23 Nov 2004 12:28:45 -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 11778 invoked from network); 23 Nov 2004 12:28:35 -0000 Received: from unknown (HELO legolas.inter.net.il) (192.114.186.24) by sourceware.org with SMTP; 23 Nov 2004 12:28:35 -0000 Received: from zaretski ([80.230.156.45]) by legolas.inter.net.il (MOS 3.5.5-GR) with ESMTP id DEH45271 (AUTH halo1); Tue, 23 Nov 2004 14:27:38 +0200 (IST) Date: Tue, 23 Nov 2004 16:24:00 -0000 From: "Eli Zaretskii" To: Daniel Jacobowitz Message-ID: <01c4d157$Blat.v2.2.2$96e70920@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 CC: gdb@sources.redhat.com In-reply-to: <20041117230803.GC22472@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 17 Nov 2004 18:08:03 -0500) Subject: Re: Breaking exceptions before stack unwind Reply-to: Eli Zaretskii References: <419A5E71.8030304@stankevitz.com> <20041117230803.GC22472@nevyn.them.org> X-SW-Source: 2004-11/txt/msg00222.txt.bz2 > 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")?