Message-Id:	<200005311805.OAA16106@delorie.com>
Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	"Parker, Ron" <rdparker AT butlermfg DOT com>
To:	Ross Smith <ross DOT s AT ihug DOT co DOT nz>, cygwin AT sourceware DOT cygnus DOT com
Subject:	RE: Major bug -- Exception handling broken
Date:	Wed, 31 May 2000 13:03:05 -0500
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2448.0)

------_=_NextPart_000_01BFCB2A.8F655AF4
Content-Type: text/plain;
	charset="iso-8859-1"

> Exception handling in g++ is totally broken in the current Cygwin
> release. Almost any program that uses exceptions crashes:
> 
> class Foo {};
> int main() {
>   try { throw Foo(); }
>   catch (const Foo&) { return 0; }
> }
> 
> $ g++ foo.cpp -o foo
> $ ./foo
> 0 [main] foo 1007 handle_exceptions: Exception: 
> STATUS_ACCESS_VIOLATION
> 5052 [main] foo 1007 stackdump: Dumping stack trace to 
> foo.exe.stackdump

I have verified that this is a bug.  Mumit Khan, the cygwin gcc guru, is out
of the country and should be back mid-June.  In the mean time I will see
what I can find.

For the time being you may work around it by replacing g++ in the command
line with gcc.  That produces a working executable.  My best guess at this
time is that there is a problem with g++ in the specs file.  I will check it
next.


------_=_NextPart_000_01BFCB2A.8F655AF4
Content-Type: text/plain; charset=us-ascii

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
------_=_NextPart_000_01BFCB2A.8F655AF4--

- Raw text -