--- Comment #6 from andriys at gmail dot com 2009-08-04 13:41 ---
(In reply to comment #5)
I cannot comment on the build of libsdc++.dll in the mingw 4.4.0 release since
I have not looked at that source.
There is a patch file that is shipped along with the mingw 4.4.0 build
--- Comment #7 from andriys at gmail dot com 2009-08-04 13:53 ---
Created an attachment (id=18296)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18296action=view)
Yet another test case
This test checks whether main executable and dll share common
abi::__cxa_eh_globals structure.
--- Comment #8 from dannysmith at users dot sourceforge dot net 2009-08-05
04:55 ---
(In reply to comment #6)
(In reply to comment #5)
Applying Dave Korn's patch mentioned in Comment #2, and linking against
libstdc++.dll, I get this with your original testcaase:
Expecting
--- Comment #5 from dannysmith at users dot sourceforge dot net 2009-08-02
08:57 ---
(In reply to comment #3)
I'm linking using g++ driver, so shared libgcc is enabled by default in 4.4.0.
I've just tried to enabled shared libstdc++ as described in the Release Notes
to the MinGW
--- Comment #3 from andriys at gmail dot com 2009-07-31 06:56 ---
I'm linking using g++ driver, so shared libgcc is enabled by default in 4.4.0.
I've just tried to enabled shared libstdc++ as described in the Release Notes
to the MinGW GCC 4.4.0 release, which made no difference.
More
--- Comment #4 from andriys at gmail dot com 2009-07-31 06:58 ---
Created an attachment (id=18277)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18277action=view)
Modified test case (not dependent on libstdc++ at all)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40918
--- Comment #1 from andriys at gmail dot com 2009-07-30 20:22 ---
Created an attachment (id=18275)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18275action=view)
Test case
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40918
--- Comment #2 from dannysmith at users dot sourceforge dot net 2009-07-31
04:18 ---
(In reply to comment #0)
I was not able to reproduce the bug on Linux, so I assume this is a
Windows-specific.
If an exception is generated inside shared library (DLL), then crosses the
