[Valgrind-users] Catching changes to a memory location

[Alex B. <ker...@be...>]

Hi,

I'm currently chasing down a bug in my application which looks like a
pointer being corrupted after being cleared.

The default Valgrind run dutifully shows the SEGV caused by following
the corrupted pointer but I'd
like a way of seeing all the places this pointer is touched. So far
adding fprintf's to the code hasn't helped which leads
me to believe its not any of the could that *should* be touching this
location. I've tried tracking it down with
gdb awatch statements but it's proving more than a little problamatic
(and very manual).

Is there any way I could mark an interesting location in memory with
the client mechanism and then get
Valgrind to show me a backtrace everytime the location was touched? If
not it would be a really useful tool :-)

-- 
Alex, homepage: http://www.bennee.com/~alex/
CV: http://www.bennee.com/~alex/cv.php