This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Breaking exceptions before stack unwind
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 23 Nov 2004 14:24:57 +0200
- Subject: Re: Breaking exceptions before stack unwind
- References: <419A5E71.8030304@stankevitz.com> <20041117230803.GC22472@nevyn.them.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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")?