https://bugs.kde.org/show_bug.cgi?id=372347
--- Comment #2 from Christopher Smith <ch...@hichris.com> --- Thanks for the reply. If you plan on making Valgrind override my delete operator as well, that could cause issues for my intermediate code. 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? 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. Would it be possible to just override malloc/free and NOT new/delete? I would expect there to be an option for this. -- You are receiving this mail because: You are watching all bug changes.
