https://bugs.kde.org/show_bug.cgi?id=398445
--- Comment #11 from Stas Sergeev <s...@list.ru> --- (In reply to Philippe Waroquiers from comment #10) > If you declare the memory initialised before forking, > using VALGRIND_MAKE_MEM_DEFINED() ... which is what my latest test-case already does. Please suggest how to improve the test-case. > But in any case, as you suggested, we should > improve the doc to mention the multi-mapping. > > Any suggestion where to put this information ? > (or asked otherwise, where did you search in > the doc ?) In google, of course. :) "valgrind memcheck false positives" or "valgrind uninitialized false positives" etc. google will find it in a wiki or in off-line docs, so whatever place you prefer, is only a question of the valgrind-established practices. google will find it anywhere. Since valgrind knows that the error comes from the shared mem, it can print more description itself, referring to the docs. In this case the user will certainly not miss it. -- You are receiving this mail because: You are watching all bug changes.
