question regarding mismatching free/delete

Hi,

I have a questing regarding Valgrind report 'Mismatched free() / delete / delete []'.

I understand that Valgrind is redirecting calls to new/delete and so on to its own. On the allocation side I see:

operator new(unsigned long) (vg_replace_malloc.c:487)

on the deallocation side

free (vg_replace_malloc.c:989)
Our new/delete operators are overloaded and call effectively malloc/free at some point.
Could it be that Valgrind can get confused and not resolve the overloaded operators correctly?

Thanks,
Thomas

_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users