https://bugs.kde.org/show_bug.cgi?id=436413
--- Comment #4 from Paul Floyd <[email protected]> --- I've been thinking about this. I don't think that there is a quick fix. Some of this may also apply to alligned alloc functions that I've also been thinking about. What needs doing? First a new option --realloc-size-zero-free=yes|no warn when realloc is used with a size of zeroy [no] I think that the REALLOC macro in vg_replace_malloc.c needs to just be a wrapper around tool.realloc and not decide what to do with different values of pointer and size. That does mean that all the tool realloc replacements will need updating. -- You are receiving this mail because: You are watching all bug changes.
