From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: minimalistic MI catch support
Date: Fri, 10 Feb 2006 20:20:00 -0000 [thread overview]
Message-ID: <20060210202045.GA610@nevyn.them.org> (raw)
In-Reply-To: <17388.62590.117990.323555@kahikatea.snap.net.nz>
On Sat, Feb 11, 2006 at 09:15:58AM +1300, Nick Roberts wrote:
> OK thanks for explaining the difference. I would still say that they are
> a _bit_ like breakpoints (they stop execution if fork or exec are called)
> and I guess thats why their details are given in "info breakpoints".
>
> Are you saying "catch fork" and "catch exec" aren't at all like
> "catch catch" and "catch throw" which do have addresses? If so, perhaps
> some clearer distinction could be made to the user/in MI output.
I think Eli's convinced me on this point; we should hide the addresses,
at least in "info breakpoints".
"catch catch" is a pretty generic concept. When implemented on a GNU
v3 binary, it uses a breakpoint; when implemented on an old HP-UX aCC
binary, apparently, it used an out-of-band event just like "catch
fork". Thus the difference.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-10 20:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 6:28 Nick Roberts
2006-02-10 6:34 ` Nick Roberts
2006-02-10 11:25 ` Eli Zaretskii
2006-02-10 14:11 ` Daniel Jacobowitz
2006-02-10 15:41 ` Eli Zaretskii
2006-02-10 16:48 ` Daniel Jacobowitz
2006-02-10 18:40 ` Eli Zaretskii
2006-02-10 18:52 ` Daniel Jacobowitz
2006-02-10 20:17 ` Nick Roberts
2006-02-10 20:20 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-28 13:04 Markus Schiltknecht
2006-02-06 23:29 ` Daniel Jacobowitz
2006-02-07 1:15 ` Bob Rossi
2006-02-07 3:00 ` Daniel Jacobowitz
2006-02-07 12:01 ` Markus Schiltknecht
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=20060210202045.GA610@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nickrob@snap.net.nz \
/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