# HG changeset patch
# User Ben Wing <ben@xemacs.org>
# Date 1263921937 21600
# Node ID 299dce99bdadccb41da279226f93a8be1c187405
# Parent  195ceb7d62297b5ef4b8bf0ceea03569c914d23b
(for main branch) when freeing check against DEADBEEF_CONSTANT since that's what we use elsewhere

diff -r 195ceb7d6229 -r 299dce99bdad src/alloc.c
--- a/src/alloc.c	Tue Jan 19 05:35:57 2010 -0600
+++ b/src/alloc.c	Tue Jan 19 11:25:37 2010 -0600
@@ -272,7 +272,7 @@
   /* Unbelievably, calling free() on 0xDEADBEEF doesn't cause an	\
      error until much later on for many system mallocs, such as		\
      the one that comes with Solaris 2.3.  FMH!! */			\
-  assert (block != (void *) 0xDEADBEEF);				\
+  assert (block != (void *) DEADBEEF_CONSTANT);				\
   MALLOC_BEGIN ();							\
 }									\
 while (0)
@@ -283,7 +283,7 @@
   /* Unbelievably, calling free() on 0xDEADBEEF doesn't cause an	\
      error until much later on for many system mallocs, such as		\
      the one that comes with Solaris 2.3.  FMH!! */			\
-  assert (block != (void *) 0xDEADBEEF);				\
+  assert (block != (void *) DEADBEEF_CONSTANT);				\
   /* You cannot free something within dumped space, because there is	\
      no longer any sort of malloc structure associated with the block.	\
      If you are tripping this, you may need to conditionalize on	\