From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24629 invoked by alias); 24 Nov 2009 15:49:12 -0000 Received: (qmail 24581 invoked by uid 48); 24 Nov 2009 15:48:59 -0000 Date: Tue, 24 Nov 2009 15:49:00 -0000 Message-ID: <20091124154859.24580.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/42159] app compiled with 4.4.2 SIGABRTs after a trivial nested throw/stack unwinding In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "vlad at demoninsight dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-11/txt/msg02067.txt.bz2 ------- Comment #3 from vlad at demoninsight dot com 2009-11-24 15:48 ------- (In reply to comment #1) > This bug doesn't appear to be present in current gcc trunk on > x86_64-apple-darwin10. > Jack, how should I interpret your comment? That all is well in 4.4.3 branch or something? Or that you cannot reproduce it on your end in 4.4.2? If one wanted to leverage darwinports how would one get a 4.4.x version of gcc that does not have this issue? It seems like a basic failure of exception hanlding mechanism. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159