https://bugs.kde.org/show_bug.cgi?id=440893
--- Comment #3 from Julian Seward <jsew...@acm.org> --- > It's strange that in my case the data block is always filled with 0's > (abort() is never called), I'm using gcc 8.5.0 and c++17. The Linux kernel is obliged to zero out all memory pages it gives to a process, since not doing so would be a massive security hole. That's quite possibly what you're observing. > Just for my information is there a reason why valgrind only complained > about the first element of the array being uninitialized, and not the > rest of the array? Because all of those accesses will have the same stack trace, and Memcheck will only show the first one. Use -v if you want per-stack-trace error counts. -- You are receiving this mail because: You are watching all bug changes.
