From: "Eli Zaretskii" <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Breaking exceptions before stack unwind
Date: Tue, 23 Nov 2004 16:24:00 -0000 [thread overview]
Message-ID: <01c4d157$Blat.v2.2.2$96e70920@zahav.net.il> (raw)
In-Reply-To: <20041117230803.GC22472@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 17 Nov 2004 18:08:03 -0500)
> 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")?
next prev parent reply other threads:[~2004-11-23 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 21:10 Chris Stankevitz
2004-11-17 23:23 ` Daniel Jacobowitz
2004-11-18 9:25 ` Chris Stankevitz
2004-11-19 3:13 ` Daniel Jacobowitz
2004-11-23 16:24 ` Eli Zaretskii [this message]
2004-11-24 4:47 ` Daniel Jacobowitz
2004-11-24 6:53 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01c4d157$Blat.v2.2.2$96e70920@zahav.net.il' \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox