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

[Jonathan Wakely]

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?