A memory bug detected by valgrind?

[huahang]

I get the following error in my program when running with valgrind to check memory issue:

==16539== Syscall param write(buf) points to uninitialised byte(s)
==16539==    at 0x554C88D: ??? (syscall-template.S:81)
==16539==    by 0x54DA002: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1261)
==16539==    by 0x54DB4DB: new_do_write (fileops.c:538)
==16539==    by 0x54DB4DB: _IO_do_write@@GLIBC_2.2.5 (fileops.c:511)
==16539==    by 0x54DA6A0: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1332)
==16539==    by 0x54CFE6C: fwrite (iofwrite.c:43)
==16539==    by 0x67B5EB: google::(anonymous namespace)::LogFileObject::Write(bool, long, char const*, int) (logging.cc:896)
==16539==    by 0x6814A7: google::LogDestination::MaybeLogToLogfile(int, long, char const*, unsigned long) (logging.cc:563)
==16539==    by 0x681503: google::LogDestination::LogToAllLogfiles(int, long, char const*, unsigned long) (logging.cc:575)
==16539==    by 0x67CA09: google::LogMessage::SendToLog() (logging.cc:1208)
==16539==    by 0x67C615: google::LogMessage::Flush() (logging.cc:1115)
==16539==    by 0x67C452: google::LogMessage::~LogMessage() (logging.cc:1082)

==16539==  Address 0x4025f6d is not stack'd, malloc'd or (recently) free'd
==16539== 

It seems to be a bug in glog?