[Python-checkins] python/dist/src/Misc SpecialBuilds.txt,1.6,1.7

[tim_one@users.sourceforge.net]

Update of /cvsroot/python/python/dist/src/Misc
In directory usw-pr-cvs1:/tmp/cvs-serv16392/python/Misc

Modified Files:
	SpecialBuilds.txt 
Log Message:
Some clarifications.


Index: SpecialBuilds.txt
===================================================================
RCS file: /cvsroot/python/python/dist/src/Misc/SpecialBuilds.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** SpecialBuilds.txt	10 Jul 2002 19:29:49 -0000	1.6
--- SpecialBuilds.txt	11 Jul 2002 00:02:52 -0000	1.7
***************
*** 81,85 ****
  8 bytes are added at each end of each block of N bytes requested.  The
  memory layout is like so, where p represents the address returned by a
! malloc-like or realloc-like function:
  
  p[-8:-4]
--- 81,87 ----
  8 bytes are added at each end of each block of N bytes requested.  The
  memory layout is like so, where p represents the address returned by a
! malloc-like or realloc-like function (p[i:j] means the slice of bytes
! from *(p+i) inclusive up to *(p+j) exclusive; note that the treatment
! of negative indices differs from a Python slice):
  
  p[-8:-4]
***************
*** 105,109 ****
      If "bad memory" is detected later, the serial number gives an
      excellent way to set a breakpoint on the next run, to capture the
!     instant at which this block was passed out.
  
  A malloc-like or free-like function first checks that the FORBIDDENBYTEs
--- 107,113 ----
      If "bad memory" is detected later, the serial number gives an
      excellent way to set a breakpoint on the next run, to capture the
!     instant at which this block was passed out.  The static function
!     bumpserialno() in obmalloc.c is the only place the serial number
!     is incremented, and exists so you can set such a breakpoint easily.
  
  A malloc-like or free-like function first checks that the FORBIDDENBYTEs
***************
*** 125,129 ****
  
  Py_DEBUG implies Py_REF_DEBUG, Py_TRACE_REFS, and PYMALLOC_DEBUG (if
! WITH_PYMALLOC is enabled).
  ---------------------------------------------------------------------------
  COUNT_ALLOCS
--- 129,135 ----
  
  Py_DEBUG implies Py_REF_DEBUG, Py_TRACE_REFS, and PYMALLOC_DEBUG (if
! WITH_PYMALLOC is enabled).  In addition, C assert()s are enabled (via
! the C way:  by not defining NDEBUG), and some routines do additional
! sanity checks inside "#ifdef Py_DEBUG" blocks.
  ---------------------------------------------------------------------------
  COUNT_ALLOCS