|
From: Nicholas N. <nj...@ca...> - 2004-02-29 00:01:17
|
On Sat, 28 Feb 2004, Robert Walsh wrote: > > Any other show-stoppers? > > If your code overrides operator new(), then 73655 is going to bite you. > I don't know how common this is, but it's definitely stopping us from > using Valgrind on our compiler at the moment. Was that introduced with Jeremy's FV changes, ie. do 2.0.0/2.1.0 work ok? > I think I know how to fix this - I just haven't sat down and thought it > through yet. Drop me an email if you want to hear to gory details. I'd be interested to hear, and you might as well tell the group while you're at it? Actually, I'm not certain what the problem is -- if a program overrides new or new[], is the idea that Valgrind's new/new[] should *not* be called... but sometimes it is? N |