public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: V.Haisman@sh.cvut.cz
To: gcc-gnats@gcc.gnu.org
Subject: c++/10135: Uncaught exceptions with --disable-sjlj-exceptions configured GCC
Date: Tue, 18 Mar 2003 13:56:00 -0000	[thread overview]
Message-ID: <20030318135046.E872C3C0B7@logout.sh.cvut.cz> (raw)


>Number:         10135
>Category:       c++
>Synopsis:       Uncaught exceptions with --disable-sjlj-exceptions configured GCC
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 18 13:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     U-AMBER2\wilx
>Release:        3.3 20030315 (prerelease)
>Organization:
>Environment:
System: CYGWIN_NT-5.1 amber2 1.3.23(0.79/3/2) 2003-03-17 22:08 i686 unknown unknown Cygwin


	
host: i686-pc-cygwin
build: i686-pc-cygwin
target: i686-pc-cygwin
configured with: ../srcdir/configure --srcdir=/cygdrive/c/WilX/gcc33/srcdir --enable-threads=posix --enable-languages=c,c++ --enable-haifa --enable-nls --without-included-gettext --enable-version-specific-runtime-libs --enable-dwarf2 --with-arch=atholn --with-cpu=athlon --disable-sjlj-exceptions
>Description:
	This testcase aborts when compiled with GCC that is configured with --disable-sjlj-exceptions option. It works when the GCC is compiled without this option.
>How-To-Repeat:
	#include <cstdio>

//void f () throw (int)
void f ()
{
  try
    {
      throw (int)1;
    }
  catch (...)
    {
      throw;
    }
}

int main () throw ()
{
  try
    {
      try
        {
          f ();
        }
      catch (...)
        {
          throw;
        }
    }
  catch (...)
    {
      printf ("exception\n");
    }
}

>Fix:
	

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-03-18 13:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030318135046.E872C3C0B7@logout.sh.cvut.cz \
    --to=v.haisman@sh.cvut.cz \
    --cc=gcc-gnats@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).