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 To: cygwin AT cygwin DOT com From: Rainer Hochreiter Subject: RE: c++ exceptions in shared library results in crash Date: Thu, 13 Jan 2005 14:16:41 +0100 Lines: 25 Message-ID: References: <001e01c4f951$7bf2bf70$6b4861cb AT DANNY> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: 193.16.155.145 User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) X-IsSubscribed: yes On Thu, 13 Jan 2005 22:23:02 +1300, Danny Smith wrote: > 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") how can i found out whether my sources hace this patch included? can you give me a hint, how to build libstdc++ and libgcc as dlls, cause i'm not really familiar with auto-import and pseudo-runtime-relocs??? Rainer -- 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/