|
From: <sv...@va...> - 2005-12-18 02:37:55
|
Author: sewardj
Date: 2005-12-18 02:37:50 +0000 (Sun, 18 Dec 2005)
New Revision: 5366
Log:
When using a custom allocator that allocates with no intervening
blocks, the <=3D relation is the correct one. In effect asserting <
constitutes an off-by-one error.
Modified:
trunk/memcheck/mac_leakcheck.c
Modified: trunk/memcheck/mac_leakcheck.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/memcheck/mac_leakcheck.c 2005-12-17 20:37:36 UTC (rev 5365)
+++ trunk/memcheck/mac_leakcheck.c 2005-12-18 02:37:50 UTC (rev 5366)
@@ -702,7 +702,7 @@
/* Sanity check -- make sure they don't overlap */
for (i =3D 0; i < lc_n_shadows-1; i++) {
tl_assert( lc_shadows[i]->data + lc_shadows[i]->size
- < lc_shadows[i+1]->data );
+ <=3D lc_shadows[i+1]->data );
}
=20
if (lc_n_shadows =3D=3D 0) {
|