Oliver Jowett <[EMAIL PROTECTED]> writes:
> Seen in passing when running valgrind against a CVS HEAD build:
>> ==28598== Syscall param write(buf) contains uninitialised or unaddressable
>> byte(s)
> Anything to be concerned about?
AFAIK this represents valgrind complaining because we have writte
Seen in passing when running valgrind against a CVS HEAD build:
==28598== Syscall param write(buf) contains uninitialised or unaddressable
byte(s)
==28598==at 0x1BABC558: write (in /lib/libc-2.3.4.so)
==28598==by 0x1BA7165D: (within /lib/libc-2.3.4.so)
==28598==by 0x1BA715FE: _IO_do_wr
