This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Major bug -- Exception handling broken
- To: "Parker, Ron" <rdparker at butlermfg dot com>, <cygwin at sourceware dot cygnus dot com>
- Subject: Re: Major bug -- Exception handling broken
- From: "Ross Smith" <ross dot s at ihug dot co dot nz>
- Date: Thu, 1 Jun 2000 09:45:05 +1200
- References: <E12xCry-0002nX-00@mx1.ihug.co.nz>
From: "Parker, Ron" <rdparker@butlermfg.com>
> > 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.
Thanks, that seems to work. Are there any gotchas I need to watch out
for when doing it this way? That is, are there any differences between
invoking via gcc vs g++ that aren't accounted for by adding -lstdc++
to the link step?
--
Ross Smith <ross.s@ihug.co.nz> The Internet Group, Auckland, New Zealand
========================================================================
"So that's 2 T-1s and a newsfeed ... would you like clues with that?"
-- Peter Da Silva
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com