https://bugs.kde.org/show_bug.cgi?id=398445
--- Comment #14 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Stas Sergeev from comment #13) > Will it help to print an additional warning when > the uninitialized mem is copied to the shared region? > The chances are very high this will result in a false-positives > later, so maybe catching it at that stage would be better? > If such warning is printed, valgrind may just consider > them initialized from now on, to avoid the false-positive > error later. > What do you think about such strategy? Giving errors/warnings when uninitialised memory is copied will as far as I can see slow down valgrind (as it means that each copy operation must contain a check) and will cause many false positive. So, IMO, the easiest is to use the client requests (the downside of this is that this implies modification of the code). -- You are receiving this mail because: You are watching all bug changes.
