https://bugs.kde.org/show_bug.cgi?id=372347
--- Comment #4 from Christopher Smith <ch...@hichris.com> --- (In reply to Philippe Waroquiers from comment #3) > 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. Certain parts of my program do a lot of allocation/deallocation. I plan on adding a sort of "cache" for same sized sections of memory to prevent having to run malloc each time. Although I suppose this is purely a performance optimization and can be omitted during testing. For now, I'll use `--show-mismatched-frees=no`. I'm looking forward to this fix. -- You are receiving this mail because: You are watching all bug changes.
