commit f798eeea5e04b96f5d0df2b74e6757e7180a6dd1
author nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Tue Apr 13 08:36:35 2004 +0000
committer nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Tue Apr 13 08:36:35 2004 +0000
tree aa8d43f0398be7f99619535f69546c30afe865ff
parent 14fa0a7772991f36b0158caf3351d30b452d95ee

Changed error message from:

  Address 0x%x is not stack'd, malloc'd or free'd

to

  Address 0x%x is not stack'd, malloc'd or (recently) free'd

This makes things clearer in some circumstances, particularly when bogusly
accessing heap memory that has been freed, but Memcheck is no longer tracking.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2358 a5019735-40e9-0310-863c-91ae7b9d1cf9

memcheck/tests/badfree.stderr.exp

diff --git a/memcheck/tests/badfree.stderr.exp b/memcheck/tests/badfree.stderr.exp
index 48ab64e..fe7c557 100644
--- a/memcheck/tests/badfree.stderr.exp
+++ b/memcheck/tests/badfree.stderr.exp
@@ -1,7 +1,7 @@
 Invalid free() / delete / delete[]
    at 0x........: free (vg_replace_malloc.c:...)
    by 0x........: main (badfree.c:12)
- Address 0x........ is not stack'd, malloc'd or free'd
+ Address 0x........ is not stack'd, malloc'd or (recently) free'd
 
 Invalid free() / delete / delete[]
    at 0x........: free (vg_replace_malloc.c:...)