https://bugs.kde.org/show_bug.cgi?id=436413
--- Comment #3 from Mark Wielaard <m...@klomp.org> --- Another interesting corner case is malloc (0), this is also implementation defined. It might either return a NULL pointer or an unique pointer (that needs to be freed). Currently valgrind doesn't warn about this, but does report such blocks as lost when not freed: definitely lost: 0 bytes in 1 blocks If we warn about realloc with size zero we might also want to warn about malloc with size zero. Both calls are suspect and might not do what the developer expects. -- You are receiving this mail because: You are watching all bug changes.
