https://bugs.kde.org/show_bug.cgi?id=398445
--- Comment #5 from Stas Sergeev <s...@list.ru> --- Think of the following use-case. Consider a very silly shm IPC that uses just one large struct with many input and output fields. Client fills in the output fields and copies the entire struct to the shm buffer. Server reads it, fills in the input fields and puts it back to shm. Client reads the struct back with all fields now properly initialized. valgrind in this scenario would still think some fields are uninitialized because it can't understand that server have already replaced the entire content in this buffer. This is what my test-case is trying to demonstrate. It doesn't matter whether the server is in the same process or another, as valgrind will behave the same way in both cases. -- You are receiving this mail because: You are watching all bug changes.
