From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: Patch: FYI: don't 'return' from TRY_CATCH
Date: Mon, 24 Aug 2009 21:14:00 -0000 [thread overview]
Message-ID: <83ab1oex9j.fsf@gnu.org> (raw)
In-Reply-To: <m3my5pvy8x.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Date: Mon, 24 Aug 2009 12:54:22 -0600
>
> I found this problem using the attached script. It is simplistic but I
> think it should catch most cases of this bug. You can run it using:
>
> emacs --script try-catch.el /path/to/src/gdb
Maybe we should have a special directory in the repository for this
stuff, which will not be tarred into the release tarballs.
prev parent reply other threads:[~2009-08-24 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 19:03 Tom Tromey
2009-08-24 21:14 ` 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=83ab1oex9j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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