https://bugs.kde.org/show_bug.cgi?id=372347
--- Comment #3 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Christopher Smith from comment #2) > Thanks for the reply. > > If you plan on making Valgrind override my delete operator as well, that > could cause issues for my intermediate code. If your new/delete operators will have the 'normal/expected' semantic, then why would the Valgrind replacement create a problem ? Or, in other words, what is special in your operators that make them non replaceable ? You lose a lot of Valgrind functionalities if you do not replace the heap functions. > One thing I could do, would be > to use the Client Request Mechanism to notify Valgrind of my memory changes, > but then disable the operator replacement. Is it possible to disable the > replacement? You can disable replacement of new/delete if they are statically linked, or if they are in a 'non standard library' (i.e. a lib different of libc.so* on linux). See user manual option --soname-synonyms=syn1=pattern1,syn2=pattern2,... for more details. > > I'm reading over the docs and it mentions VALGRIND_CREATE_MEMPOOL. If I'm > running on Linux, I wouldn't have access to that. I do not understand what you mean with this "wouldn't have access to that." > Would it be possible to > just override malloc/free and NOT new/delete? I would expect there to be an > option for this. There is no specific option to do partial replacement of some allocation functions. -- You are receiving this mail because: You are watching all bug changes.
