Crash due to mis-bind of a libstdc++ symbol

[Mike Hearn <mike at navi dot cx>]

Hi,

I posted to the GCC list about a crash caused by a symbol mis-bind in a
multi-ABI binary: a setup similar to that described in the "Testing
multi-ABI binaries" section of the libstdc++ ABI guide:

   http://gcc.gnu.org/ml/gcc/2005-04/msg00928.html

I was advised in private to post here too, in case the libstdc++
maintainers missed it.

I haven't fully investigated what is going on here, but for some reason a
v5 symbol takes precedence over the v6 symbol despite the use of symbol
versioning. I am pretty sure it's a bug, but I'm not sure where:

- libstdc++ itself
- the dynamic linker
- the compile-time linker

... seem the most likely options. 

This is a serious problem, as it makes it impossible to reliably
distribute C++ binaries even if they only import C APIs.

thanks -mike