On 8/25/2014 16:50, Yaron Keren wrote: > Hi Ruben, > > Thanks for pointing this out, the problem is indeed that libstdc++ is > linked to the dynamic ligcc while the program (as above) links to the > static version of libgcc. There are two seperate copies of libgcc that do > not share exception information resulting in uncaught exception. > > If -static is added than only one static copy of libgcc is linked and the > exception is caught. > > Could the compiler enforce "If you link to static libgcc, you should also > link libstdc++ statically" or at least warn about it? > It would save users such mysterious bugs resulting from having two copies > of ligcc around.
Unfortunately, no, binutils doesn't have any notion of what the input files to the linker mean. Doesn't stop users from doing it though.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/
_______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
