> I am not a valgrind expert so, take the following with a grain of salt > but I think that the above statement is wrong: valgrind reliably detects > use of uninitialized variables if you define 'use' as meaning 'affects > control flow of your program' in valgrind.
It works in some cases for the stack, but not in all. Consider the redzone on the x86-64 ABI. How should valgrind distingush an uninitialized redzone variable from a initialized one if the stack has been used before? I didn't even think it worked in all cases for variables in the real frame. You're right my example was bogus because it didn't test the control flow. -Andi -- a...@linux.intel.com -- Speaking for myself only.
