From: "Eli Zaretskii" <eliz@gnu.org>
To: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>
Cc: cagney@gnu.org, kettenis@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Use TRY_CATCH in wrapper.c
Date: Thu, 17 Feb 2005 00:32:00 -0000 [thread overview]
Message-ID: <01c51469$Blat.v2.4$e96bb9c0@zahav.net.il> (raw)
In-Reply-To: <7319934860044785@weblx058.utsp.utwente.nl> (m.m.kettenis@alumnus.utwente.nl)
> From: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>
> Date: Wed, 16 Feb 2005 13:30:00 +0000
>
> > > Am I right in assuming that TRY_CATCH was added to make things like
> > > this possible? It sure cleans things up up ;-).
> >
> > Yes, exactly. These cleanups, assuming before/after test results are
> > identical, should be treated as obvious.
>
> Thanks.
>
> I was a bit confused since only the function in exceptions.c used the stuff.
I think there's another reason why you were confused: because
TRY_CATCH is not documented in gdbint.texinfo.
prev parent reply other threads:[~2005-02-16 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 3:38 Mark Kettenis
2005-02-16 14:26 ` Andrew Cagney
2005-02-16 14:43 ` M.M. Kettenis
2005-02-17 0:32 ` 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='01c51469$Blat.v2.4$e96bb9c0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.org \
--cc=m.m.kettenis@alumnus.utwente.nl \
/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