strange segfaults / valgrind errors / invalid free on string ::_Rep::_S_empty_rep_storage

[Paweł Sikora]

On Wednesday 01 of August 2012 19:57:25 Jonathan Wakely wrote:
> On 1 August 2012 14:59, Paweł Sikora wrote:
> > i have no idea why the string implementation tries to destroy static _S_empty_rep_storage area?
> 
> This usually implies some objects were compiled by GCC configured with
> --enable-fully-dynamic-string and some objects were compiled by a
> different GCC configured without that option.  That option changes the
> ABI, so you can't mix objects with an without it.
> 
> Could that be the cause?

all used libraries and the main application are built with the same linux toolchain
configured without fully-dynamic-string and with versioned libstdc++ namespace.
these pieces works pretty fine without any gpf/valgrind error in so called "release"
build (without _DEBUG _GLIBCXX_DEBUG).