[Valgrind-developers] Change to "not stack'd, alloc'd or (recently) free'd"

[Nicholas N. <nj...@ca...>]

Hi,

Background for this is http://bugs.kde.org/show_bug.cgi?id=78729.

Basically, a user was confused because they accessed a free'd heap block
after Valgrind had recycled it.  So I propose inserting "(recently)" in
the message about an address being "not stack'd, alloc'd or (recently)
free'd", to make it more comprehensible what might have happened.

It's a trivial code change.  Any complaints about this change to error
formats?  I'll commit in a day or two if not.

N