https://bugs.kde.org/show_bug.cgi?id=398445
--- Comment #2 from Stas Sergeev <s...@list.ru> --- Created attachment 114889 --> https://bugs.kde.org/attachment.cgi?id=114889&action=edit 2-process test-case Hi, thanks for your reply. Here is the test-case that does the same thing but with 2 processes scheme. Same valgrind error. While the first test-case represents my real program more, I really see no difference. As for the difficulty of fixing this - yes, I perfectly understand it. While I can think of some ugly work-arounds (like, for example, checking if the values have changed, and consider them initialized in that case), nothing good can probably be done. How about downgrading the error to warning if it comes from the shared mem? -- You are receiving this mail because: You are watching all bug changes.
