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
Message-ID: <018201bfcb49$7caa9b30$a8a11dcb@ihug.co.nz>
From: "Ross Smith" <ross DOT s AT ihug DOT co DOT nz>
To: "Parker, Ron" <rdparker AT butlermfg DOT com>, <cygwin AT sourceware DOT cygnus DOT com>
References: <E12xCry-0002nX-00 AT mx1 DOT ihug DOT co DOT nz>
Subject: Re: Major bug -- Exception handling broken
Date: Thu, 1 Jun 2000 09:45:05 +1200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600

From: "Parker, Ron" <rdparker AT butlermfg DOT 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 DOT s AT ihug DOT co DOT 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 AT sourceware DOT cygnus DOT com