Can't see the actual vars

Hello Everyone,
I am seeing messages like this:
--3232-- REDIR: 0x49bf990 (libc.so.6:strncat) redirected to 0x482d71c
(strncat)
==3232== Syscall param stat64(file_name) points to uninitialised byte(s)
==3232==    at 0x49FD6B8: _xstat (xstat.c:48)
==3232==    by 0x41F23: stat (stat.c:51)
==3232==    by 0x1EC93: getList (util.c:1379)
==3232==    by 0x18E0F: _get_var (ngr.c:3868)
==3232==    by 0x19F33: get_var (ngr.c:4049)
==3232==    by 0xBB4F: main (daemon.c:346)
==3232==  Address 0x7d87ba8c is on thread 1's stack
==3232==  in frame #2, created by getList (util.c:1300)
==3232==  Uninitialised value was created by a stack allocation
==3232==    at 0x1E55C: getList (util.c:1300)

Looking at line 1379 from util.c:
if (!stat(listfile, &statbuf))

listfile does exist.
statbuf however, is simply defined as: struct stat statbuf;
It's not initialized by memset or something, is that what valgrind
complains about? Thanks,
Reinoud.

_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users