Re: [Valgrind-users] Finding illegal memory accesses when Valgrind fails via an assertion

[Stephen T. <st...@to...>]

On Sat, 2007-03-31 at 02:44 +0100, Olly Betts wrote:
> No, add calls to the macro VALGRIND_CHECK_MEM_IS_DEFINED passing it
> details of the variable you want to check definedness of.  As the URL I
> referred you to above says, the comments in memcheck.h document what the
> parameters are.
> 
> > and then put #include <valgrind/memcheck.h> any where in the program
> > or in all the files?
> 
> In any files where you use VALGRIND_CHECK_MEM_IS_DEFINED.
> 
> Cheers,
>     Olly

Ok. I understand more of what you mean now. What is the strategy you
advise using this macro? I know I could go wild with putting it
everywhere. Can you show me an example of how you use it? I would like
to see how this works for debug release and a optimized release.

Stephen