Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 13 Jan 2005 22:23:02 +1300 From: Danny Smith Subject: RE: c++ exceptions in shared library results in crash To: Cygwin Cc: rainer@hochreiter.at Reply-to: Danny Smith Message-id: <001e01c4f951$7bf2bf70$6b4861cb@DANNY> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 7bit 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/