https://bugs.kde.org/show_bug.cgi?id=398445
Ivo Raisr <iv...@ivosh.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iv...@ivosh.net
--- Comment #6 from Ivo Raisr <iv...@ivosh.net> ---
(In reply to Stas Sergeev from comment #5)
> 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.
Yes, indeed. That's why we have syscall and ioctl wrappers in Valgrind.
They describe what the other side (kernel) expects from the buffers sent there
and in what shape they come back with buffers received.
It should be quite easy to extend this mechanism to an arbitrary client-server
protocol, be it via shm, sockets or any other IPC.
--
You are receiving this mail because:
You are watching all bug changes.
