public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/41174] uncaught_exception always returns true
Date: Wed, 26 Aug 2009 16:18:00 -0000	[thread overview]
Message-ID: <20090826161803.11049.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41174-18113@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from redi at gcc dot gnu dot org  2009-08-26 16:17 -------
(In reply to comment #1)
> Note that GoodE doesn't cause the problem. The difference is that BadE has a
> function-try-block

And, of course, that the exception is rethrown by BadE at the end of the
handler. Changing GoodE to rethrow makes it have the same behaviour, so it's
not specific to function-try-blocks.

I give up for now, I'll just link to bug 10606 and
http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_active.html#475 for reference


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41174


  parent reply	other threads:[~2009-08-26 16:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26  6:20 [Bug c++/41174] New: " wwashby at earthlink dot net
2009-08-26 15:31 ` [Bug c++/41174] " redi at gcc dot gnu dot org
2009-08-26 15:52 ` redi at gcc dot gnu dot org
2009-08-26 16:01 ` redi at gcc dot gnu dot org
2009-08-26 16:18 ` redi at gcc dot gnu dot org [this message]
2009-08-26 16:50 ` redi at gcc dot gnu dot org
2009-08-27 10:37 ` [Bug libstdc++/41174] " redi at gcc dot gnu dot org
2009-08-27 10:51 ` paolo dot carlini at oracle dot com
2009-08-27 11:37 ` redi at gcc dot gnu dot org
2009-08-27 11:59 ` paolo dot carlini at oracle dot com
2009-08-27 12:18 ` redi at gcc dot gnu dot org
2009-08-27 14:27 ` wwashby at earthlink dot net
2009-08-27 15:19 ` redi at gcc dot gnu dot org
2009-08-29 11:27 ` wwashby at earthlink dot net
2009-08-29 12:50 ` wwashby at earthlink dot net
2010-01-08 19:14 ` paolo dot carlini at oracle dot com

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=20090826161803.11049.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).