@@ -78,22 +78,16 @@ Py_DEBUG
7878
7979This is what is generally meant by "a debug build" of Python.
8080
81- Py_DEBUG implies LLTRACE and Py_REF_DEBUG. In addition, C assert()s are enabled
81+ Py_DEBUG implies Py_REF_DEBUG. In addition, C assert()s are enabled
8282(via the C way: by not defining NDEBUG), and some routines do additional sanity
8383checks inside "#ifdef Py_DEBUG" blocks.
8484
85-
86- LLTRACE
87- -------
88-
89- Compile in support for Low Level TRACE-ing of the main interpreter loop.
90-
91- When this preprocessor symbol is defined, before PyEval_EvalFrame executes a
92- frame's code it checks the frame's global namespace for a variable
93- "__lltrace__". If such a variable is found, mounds of information about what
94- the interpreter is doing are sprayed to stdout, such as every opcode and opcode
95- argument and values pushed onto and popped off the value stack.
96-
97- Not useful very often, but very useful when needed.
98-
99- Py_DEBUG implies LLTRACE.
85+ Also, compile in support for "lltrace" (Low Level TRACE-ing) of the main
86+ interpreter loop. Before _PyEval_EvalFrameDefault executes a frame's code, it
87+ checks the frame's global namespace for a variable "__lltrace__" (as well as for
88+ the environment variable PYTHON_LLTRACE"). If such a variable is found, mounds
89+ of information about what the interpreter is doing are sprayed to stdout, such
90+ as every opcode and opcode argument and values pushed onto and popped off the
91+ value stack. Higher integer values for the environment variable result in more
92+ and more detail being printed (the global __lltrace__ always enables the maximum
93+ output). Not useful very often, but *very* useful when needed.
0 commit comments