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 Message-ID: <005701bfca91$4475c220$a8a11dcb@ihug.co.nz> From: "Ross Smith" To: Subject: Major bug -- Exception handling broken Date: Wed, 31 May 2000 11:46:25 +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 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 System is NT4+sp6a; CPU is PIII/450; Cygwin installation is straight from the current setup.exe. If you need any more details let me know. (I reported this last week, but nobody paid any attention.) -- Ross Smith 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