Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3CC51911.3010601@goingware.com> Date: Tue, 23 Apr 2002 03:19:29 -0500 From: "Michael D. Crawford" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020214 X-Accept-Language: en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: c++ char exceptions Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit It aborts with g++ 2.95.4 on Debian PowerPC Linux too. But if I compile it with CodeWarrior 6 on Windows it runs normally, doesn't crash, and gives the exit code of 1. I think CodeWarrior is correct, and that this is a bug in g++, but not in cygwin. Mike Thus it was written: I don't know if this is a cygwin issue or if I am doing something fundamentally wrong... int main (int argc, char **argv) { try { throw "catch this"; } catch (char *message) { return 1; } return 0; } coredumps on me. Throwing int's works fine. Throwing (string) "foo" works fine. --- Michael D. Crawford GoingWare Inc. - Expert Software Development and Consulting http://www.goingware.com/ crawford AT goingware DOT com Tilting at Windmills for a Better Tomorrow. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/