From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12692 invoked by alias); 9 Jan 2008 03:19:08 -0000 Received: (qmail 12550 invoked by uid 48); 9 Jan 2008 03:18:23 -0000 Date: Wed, 09 Jan 2008 05:28:00 -0000 Message-ID: <20080109031823.12549.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/34684] Cross DLL Exceptions In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "brian at dessent dot net" 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: 2008-01/txt/msg00817.txt.bz2 ------- Comment #3 from brian at dessent dot net 2008-01-09 03:18 ------- FSF gcc does not currently support exceptions across shared libraries on Cygwin or MinGW. This is because a shared libgcc is required, and libgcc only builds static on those platforms. For the 3.4 gcc releases that MinGW and Cygwin ship, there is a local patch that lets exceptions across shared libraries work with static libgcc. This patch is quite a hack and was offered but never accepted upstream. It cannot be used with 4.x because the internals have changed so much. The real solution is to build libgcc shared, which is what the MinGW gcc 4.2 release does with a number of MinGW-local patches. They have not made their way into FSF gcc, so until somebody works on this FSF gcc will continue to be broken. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34684