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: <4.3.1.2.20000526091706.00c0d060@po00.nada.kth.se> X-Sender: d94-llu AT po00 DOT nada DOT kth DOT se X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 26 May 2000 09:21:40 +0200 To: "Ross Smith" , From: Leif Lundgren Subject: Re: G++ bug in Cygwin 1.1.1 In-Reply-To: <03d301bfc69d$13ebd150$a8a11dcb@ihug.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed At 11:00 2000-05-26 +1200, Ross Smith wrote: >This short program: > >class Foo {}; >int main() { > try { throw Foo(); } > catch (const Foo&) { return 0; } >} > >compiled with the version of g++ 2.95.2 that comes with the current >net distribution, crashes when run: > >$ ./foo.exe >0 [main] foo 1007 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION >5052 [main] foo 1007 stackdump: Dumping stack trace to foo.exe.stackdump > >This doesn't show up with the same compiler on Linux, suggesting that >this is either a Cygwin bug, or a g++ bug that only shows up on some >operating systems. I had similar probems after installing the current snapshots. The cause was conflicting versions of cygwin1.dll. Run "cygcheck -s" to check. /Leif -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com