Julian Foad <julian.f...@wandisco.com> writes: > Philip Martin wrote: >> $ svnadmin create repo >> $ valgrind -q --num-callers=20 subversion/svn/.libs/lt-svn import -mm >> subversion/tests/cmdline/theta.bin file://`pwd`/repo/f1 >> ==15201== Syscall param write(buf) points to uninitialised byte(s) > > Yup, similar result here running a recent trunk build.
I think this is a false alarm. It occurs when writing zlib compressed svndiff data and I'm using zlib 1.2.3.3. I know this version of zlib gives valgrind warnings during compression, and I think that the way the zlib algorithm works means that it doesn't affect the result of a compression-decompression round trip. -- Philip
