Re: [Valgrind-developers] Bug 73655 fix

[Nicholas N. <nj...@ca...>]

On Tue, 13 Apr 2004, Robert Walsh wrote:

> The test is borked.  new Test[2] doesn't ever call the operator new
> defined in that file because it's looking for operator new[] instead.
> I'll fix the test in the patch and make a new release of the patch later
> tonight.

So if a program has its own version of new or new[], Valgrind doesn't know
anything about them, and any heap blocks allocated with them won't be
checked as normal?  Is it possible to have a custom 'new' but a non-custom
'delete'?  That could cause false free errors?

N