https://bugs.kde.org/show_bug.cgi?id=398445
--- Comment #17 from Stas Sergeev <s...@list.ru> --- (In reply to Philippe Waroquiers from comment #16) > That might not be straightforward to do, in particular if you have > multiple threads (you probably need a critical section around the > write operations) or processes (this will even be more complex, as you > will probably need a side channel to inform all other processes about what > was done). Exactly, that's the point. You need a side-channel that also knows about the relationship between the pointers to shm in different processes - something only the kernel knows about normally (a bit simpler if shm is mapped before fork() - then the pointers are equal, but this is not always the case). Thant's why I think VALGRIND_MAKE_MEM_DEFINED doesn't actually work for this case, and yet you suggested it all along the way here (and I was updating the test-case) and also in the docs. So I think there is some mistake. This all seems to suggest it might be better to enable the errors from shm with some extra command-line switch, leaving it disabled by default... -- You are receiving this mail because: You are watching all bug changes.
