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.

Ah, of course.

> First, the problem: the problem was that Valgrind was always
> intercepting operator new, even when your program defined it's own
> version of it.  This is why new_override.cpp would never have worked
> even if it had been overriding operator new[].
[snip]
> Does that make sense?

Sounds plausible.  Is it documented?  I'm not sure if the comments in
vg_intercept.vgi now match with the reality.  A precis of your description
could be what's needed...

Also, I see in the generated vg_intercept.c lines like this:

  int VG_INTERCEPT(soname$3Alibc$2Eso$2E6$3A__raise)(int)

How does that work?  What's with the dollar signs?

N