1

Valgrind cannot locate stack allocation for uninitialised data

view story
linux-howto

http://stackoverflow.com – I have a a single error when I run my program through valgrind. The problem is that it wont tell me where the uninitialised bytes were allocated: ==22141== Syscall param write(buf) points to uninitialised byte(s) ==22141== at 0x5B68900: __write_nocancel (syscall-template.S:82) ==22141== by 0x5AFB882: _IO_file_write@@GLIBC_2.2.5 (fileops.c:1289) ==22141== by 0x5AFB749: new_do_write (fileops.c:543) ==22141== by 0x5AFCEB4: _IO_do_write@@GLIBC_2.2.5 (fileops.c:516) ==22141== by 0x5AFDD3E: _IO_switch_to_get_mode (genops.c:189) ==22141== by 0x5AFBA96: _IO_file_seekoff@@GLIBC_2.2.5 (HowTos)