[Bug c++/34684] Cross DLL Exceptions
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34684 Kai Tietz ktietz at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||ktietz at gcc dot gnu.org Resolution||FIXED --- Comment #4 from Kai Tietz ktietz at gcc dot gnu.org 2010-09-24 21:08:50 UTC --- For gcc version 4.5.x and newer mingw/cygwin targets are supporting shared version of libgcc and libstdc++ OOTB. By using them (see option -shared-libgcc/libstdc++) cross-DLL throw/catch is working. The static variant is still not working. This could be solved by using SEH unwinding, which isn't a feature of gcc for 32-bit x86 at the moment. So I close this bug, as there is now a working way to handle this problem -- Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug.
[Bug c++/34684] Cross DLL Exceptions
--- 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
