[Python-checkins] python/dist/src/Misc SpecialBuilds.txt,1.10,1.11

[mwh@users.sourceforge.net]

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

Modified Files:
	SpecialBuilds.txt 
Log Message:
add description of LLTRACE.


Index: SpecialBuilds.txt
===================================================================
RCS file: /cvsroot/python/python/dist/src/Misc/SpecialBuilds.txt,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** SpecialBuilds.txt	11 Jul 2002 01:04:32 -0000	1.10
--- SpecialBuilds.txt	30 Jul 2002 09:49:29 -0000	1.11
***************
*** 136,146 ****
  This is what is generally meant by "a debug build" of Python.
  
! 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                                            introduced in 0.9.9
!                                              partly broken in 2.2 and 2.2.1
  
  Each type object grows three new members:
--- 136,146 ----
  This is what is generally meant by "a debug build" of Python.
  
! Py_DEBUG implies LLTRACE, 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 introduced in 0.9.9 partly broken in 2.2 and 2.2.1
  
  Each type object grows three new members:
***************
*** 187,188 ****
--- 187,200 ----
      most recently is at the front of the list.
  ---------------------------------------------------------------------------
+ LLTRACE                                    introduced ...?  Long time ago!
+ 
+ Compile in support of Low Level TRACE-ing of the man interpreter loop.
+ 
+ When this preprocessor symbol is defined, before eval_frame
+ (eval_code2 before 2.2) executes a frame's code checks its global
+ namespace for a variable "__lltrace__".  If such a variable is found,
+ mounds of information about what the interpreter is doing are sprayed
+ to stdout, such as every opcode and opcode argument and values pushed
+ onto and popped off the value stack.
+ 
+ Not useful very often, but very useful when needed.