https://bugs.kde.org/show_bug.cgi?id=398445
--- Comment #19 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Philippe Waroquiers from comment #18) > When a 'usage of undefined' bit is detected, > it is not known anymore that this undefined > value came from (or through) shared memory, Which made me think that VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE is in fact useless, so I removed this from the doc, Always good to have enthusiastic discussions :). So currently, this then only leaves us with MAKE_MEM_DEFINED approach (in the worst case, declare your shared memory initialised before each access). -- You are receiving this mail because: You are watching all bug changes.
