2 Mar
2004
2 Mar
'04
6:06 p.m.
On Tue, Mar 02, 2004 at 11:40:06PM +0100, David Hedbor @ Pike developers forum wrote:
The "uninitialized value" issue is one that I can't seem to avoid.
Why it is difficult to avoid? Simple explicit initialization of anything (which is allocated) won't do the trick?
Sure, there are some cases when initialization is not necessary (upon allocation), but for objects which produce such warnings it might be a solution...
What I can't understand in this specific case (looked in gdb) - everything (which is referenced) seems to be initialized (n->tree_info)...
But it could be that the bug is in valgrind, though :)
Regards, /Al