https://bugs.kde.org/show_bug.cgi?id=398445
--- Comment #10 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Stas Sergeev from comment #8) > > Initialising yourself the memory via one ptr > > but accessing it via another mapping > > is not the same as declaring the memory > > defined after *each* mmap. > > In the first case, valgrind can just detect that > > the memory at ptr1 address is initialised, > > but it cannot see this initialisation via > > the second mapping. > > Well, my last test-case does only one mmap() > and then fork(). If you declare the memory initialised before forking, using VALGRIND_MAKE_MEM_DEFINED() both the parent and the child valgrind will consider it initialised. 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 ?) Thanks -- You are receiving this mail because: You are watching all bug changes.
