Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 13 Jan 2005 22:23:02 +1300
From:	Danny Smith <dannysmith AT clear DOT net DOT nz>
Subject:	RE: c++ exceptions in shared library results in crash
To:	Cygwin <cygwin AT cygwin DOT com>
Cc:	rainer AT hochreiter DOT at
Reply-to:	Danny Smith <dannysmith AT users DOT sourceforge DOT net>
Message-id:	<001e01c4f951$7bf2bf70$6b4861cb@DANNY>
MIME-version:	1.0

From: "Rainer Hochreiter"
--------------------------------------------------------------------------------

> throwing an exception in the shared library results in a core dump of the
> binary executable - but only for the cross-compiled version!

cygwin and mingw gcc sources contain a local patch to allow
throwing C++ exceptions across dll/exe boundaries. These
local hacks have never been submitted to FSF GCC lists. Without
this patch, one option you have to allow exceptions across dll/exe
boudaries is to build libstdc++.a and libgcc.a as dlls. This is not done by GCC
makefiles, but can be done done manually. Libstdc++ dll  relies on auto-import
functionality, so watch your pseudo-runtime-relocs (a techno name for "blue
psuede shoes")

Someone may well ask why this local patchset has not been
submitted for review on GCC lists, and that would be a good
question.  My answer would be that they need more work before
submission..

Danny






--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -