Julian Foad 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 h
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 buil
This came up while investigating a corrupt repository. I don't know if
the warning is connected to the corruption, or even if it is serious.
I'm using Subversion 1.6.x and apr/aprutil 1.2.12, all built with pool
debugging, but this happens with Subversion trunk as well.
The warning can be triggere
3 matches
Mail list logo
