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: Wed, 24 Nov 2004 06:53:00 -0000 [thread overview]
Message-ID: <01c4d1f1$Blat.v2.2.2$16905de0@zahav.net.il> (raw)
In-Reply-To: <20041124040237.GA24202@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 23 Nov 2004 23:02:37 -0500)
> Date: Tue, 23 Nov 2004 23:02:37 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb@sources.redhat.com
>
> the right thing to do is to document 'catch catch' and 'catch
> throw'.
They are already documented. The obsolete advice that the OP was
citing is at the end of the node which describes them. That advice is
for the case where one wants to stop the program _before_ the
exception handler is called. See the node "Set Catchpoints" in the
manual.
Given this, what would be the best way to fix the manual?
prev parent reply other threads:[~2004-11-24 6:47 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
2004-11-24 4:47 ` Daniel Jacobowitz
2004-11-24 6:53 ` Eli Zaretskii [this message]
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='01c4d1f1$Blat.v2.2.2$16905de0@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