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

[<pa...@fr...>]

----- Original Message -----
> 
> 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?


Hi David

Could you post an extract of the results?

Just to eliminate a few things. The string instance isn't itself newed?

I.e, you aren't doing something like

std::string* ps = new std::string;
...

free(ps);

I guess you would have seen this before.

You aren't overloading any operator new or delete or using placement new? You're using the default allocator std::allocator<char>?

Regards
Paul