[Valgrind-users] Mismatched free/delete with GCC 4.8.3 std::string

[David C. <dc...@gm...>]

Hi,

I've recently switched over to Valgrind 3.10.1 and I'm now see vast numbers
of 'mismatched free/delete' type messages all coming from std::string
shipped with GCC 4.8.3.

I really don't believe what Valgrind is saying but I'd like to be certain.
Firstly, has anyone else seen this behaviour recently and secondly what
criteria does Valgrind use to determine if a mismatch occurred?  Is it
possible to print out more information from Valgrind about its decision
process?

Many thanks,
David.