This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Major bug -- Exception handling broken
- To: cygwin at sourceware dot cygnus dot com
- Subject: Re: Major bug -- Exception handling broken
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Wed, 31 May 2000 16:15:40 -0400
- References: <200005311805.LAA13613@cygnus.com>
- Reply-To: cygwin at sourceware dot cygnus dot com
On Wed, May 31, 2000 at 01:03:05PM -0500, Parker, Ron wrote:
>> 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.
I may be wrong but I believe that Mumit is well-aware that structured
exception handling is broken on Windows.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com