https://bugs.kde.org/show_bug.cgi?id=440893
Tom Hughes <t...@compton.nu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
CC| |t...@compton.nu
Resolution|--- |NOT A BUG
--- Comment #1 from Tom Hughes <t...@compton.nu> ---
I think you are confused...
When there is no initializer the array new operator in C++ performs default
initialization of each member of the array
(https://en.cppreference.com/w/cpp/language/new#Construction).
Default initialization for POD types like char does nothing
(https://en.cppreference.com/w/cpp/language/default_initialization).
Therefore that memory is uninitialized and valgrind is correct.
--
You are receiving this mail because:
You are watching all bug changes.
