[Bug c++/34684] New: Cross DLL Exceptions

[Bug c++/34684] New: Cross DLL Exceptions

[XuHotdogs at gmail dot com]

Exceptions cannot escape DLL boundaries, that is, when I throw an exception in
one DLL and place a try/catch block in another EXE executable that dynamically
loads the DLL, the exception cannot be catched! Instead, the system issues an
error message and abort.
I noticed that this problem was once fixed in one of the MinGW Project's
releases, but the patch was not merged into GCC's main development sources.
Can anyone tell me what I can do or just fix the problem?
Thanks a lot!


-- 
           Summary: Cross DLL Exceptions
           Product: gcc
           Version: 4.2.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: XuHotdogs at gmail dot com
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-mingw32
GCC target triplet: i686-pc-mingw32


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34684

[Bug target/34684] Cross DLL Exceptions

[pinskia at gcc dot gnu dot org]

------- Comment #1 from pinskia at gcc dot gnu dot org  2008-01-06 12:29 -------
This is a target specific issue.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|c++                         |target


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34684

[Bug target/34684] Cross DLL Exceptions

[XuHotdogs at gmail dot com]

------- Comment #2 from XuHotdogs at gmail dot com  2008-01-06 17:18 -------
(In reply to comment #1)
> This is a target specific issue.
> Yet in MinGW's release 3.4.5, the problem got solved. I don't know why this happened again in GCC's official release 4.2.*.
Are there anyone having the same problems?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34684

[Bug c++/34684] Cross DLL Exceptions

[brian at dessent dot net]

------- 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