Hunting for buffer overflows

Is there a way to use a debugger (immunity preferably but I'll take gdb or any other debugger you know how to do this with) so that any time a piece of memory holds a particular value (say AAAAAAAA) the debugger will make a note of what line it happened and then continue on until it fully crashes.

Not just a simple watch but anytime any register or memory in use by the program contains an A to make a notation of this.  It seems like a really good idea that would take some of the hard work out of exploit development but I have yet to see any straightforward talk of this.

>>9
Good idea
>>7
The idea being that I feed crap information like 5000 A's and see where in memory those A's end up and then who tries to read or execute those A's

Then I consider the implications of being able to write into that memory

Then I use a unique pattern of the same size to identify which As were getting spewed around in memory.