Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Wed, 31 May 2000 16:15:40 -0400 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Major bug -- Exception handling broken Message-ID: <20000531161540.E24396@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com References: <200005311805 DOT LAA13613 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200005311805.LAA13613@cygnus.com>; from rdparker@butlermfg.com on Wed, May 31, 2000 at 01:03:05PM -0500 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 AT sourceware DOT cygnus DOT com