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/mac_needs.c

diff --git a/memcheck/mac_needs.c b/memcheck/mac_needs.c
index a3ab823..22e8e53 100644
--- a/memcheck/mac_needs.c
+++ b/memcheck/mac_needs.c
@@ -238,7 +238,7 @@
                "  v 2.96 or 3.0.X.  To suppress, use: --workaround-gcc296-bugs=yes");
 	 } else {
             VG_(message)(Vg_UserMsg, 
-               " Address 0x%x is not stack'd, malloc'd or free'd", a);
+               " Address 0x%x is not stack'd, malloc'd or (recently) free'd",a);
          }
          break;
       case Freed: case Mallocd: case UserG: {