Re: Breaking exceptions before stack unwind

[Daniel Jacobowitz <drow@false.org>]

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 <drow@false.org>
> > 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