https://bugs.kde.org/show_bug.cgi?id=398445
--- Comment #13 from Stas Sergeev <s...@list.ru> --- Will it help to print an additional warning when the uninitialized mem is copied to the shared region? The chances are very high this will result in a false-positives later, so maybe catching it at that stage would be better? If such warning is printed, valgrind may just consider them initialized from now on, to avoid the false-positive error later. What do you think about such strategy? -- You are receiving this mail because: You are watching all bug changes.
