Hi,
I did some basic testing of valgrind on amd64 and it seems to be in
better shape than before, at least for memory leak detection.
But I do seem to get a report on every syscall done. One example:
==7218== Use of uninitialised value of size 8
==7218== at 0x4A7670E: write (sys/w_write.c:28)
==7218== by 0x4A40F52: __sflush (stdio/fflush.c:80)
==7218== by 0x4A94726: __sfvwrite (stdio/fvwrite.c:191)
==7218== by 0x4ACCA68: __sprint (stdio/vfprintf.c:111)
==7218== by 0x4ACCA68: __vfprintf (stdio/vfprintf.c:1107)
==7218== by 0x4AC8851: vfprintf (stdio/vfprintf.c:266)
==7218== by 0x4A7C8A0: printf (stdio/printf.c:44)
==7218== by 0x109AB8: main (x.c:14)
Is there a way to avoid this? If so, it would be nice to mention that
in a pkg-readme.
-Otto
