Issue #29392: Prevent crash when passing invalid arguments into msvcrt module.

1 files changed, 4 insertions, 30 deletions

diff --git a/Misc/SpecialBuilds.txt b/Misc/SpecialBuilds.txt
index 3004174bcd..82fa23e1a7 100644
--- a/Misc/SpecialBuilds.txt
+++ b/Misc/SpecialBuilds.txt
@@ -65,9 +65,9 @@ sys.getobjects(max[, type])
     simply by virtue of being in the list.
 
 envvar PYTHONDUMPREFS
-    If this envvar exists, Py_Finalize() arranges to print a list of all
+    If this envvar exists, Py_FinalizeEx() arranges to print a list of all
     still-live heap objects.  This is printed twice, in different formats,
-    before and after Py_Finalize has cleaned up everything it can clean up.  The
+    before and after Py_FinalizeEx has cleaned up everything it can clean up.  The
     first output block produces the repr() of each object so is more
     informative; however, a lot of stuff destined to die is still alive then.
     The second output block is much harder to work with (repr() can't be invoked
@@ -144,7 +144,7 @@ Special gimmicks:
 
 envvar PYTHONMALLOCSTATS
     If this envvar exists, a report of pymalloc summary statistics is printed to
-    stderr whenever a new arena is allocated, and also by Py_Finalize().
+    stderr whenever a new arena is allocated, and also by Py_FinalizeEx().
 
 Changed in 2.5:  The number of extra bytes allocated is 4*sizeof(size_t).
 Before it was 16 on all boxes, reflecting that Python couldn't make use of
@@ -179,7 +179,7 @@ Each type object grows three new members:
      */
     int tp_maxalloc;
 
-Allocation and deallocation code keeps these counts up to date.  Py_Finalize()
+Allocation and deallocation code keeps these counts up to date.  Py_FinalizeEx()
 displays a summary of the info returned by sys.getcounts() (see below), along
 with assorted other special allocation counts (like the number of tuple
 allocations satisfied by a tuple free-list, the number of 1-character strings
@@ -234,29 +234,3 @@ When this symbol is defined, the ceval mainloop and helper functions count the
 number of function calls made.  It keeps detailed statistics about what kind of
 object was called and whether the call hit any of the special fast paths in the
 code.
-
-
-WITH_TSC
---------
-
-Super-lowlevel profiling of the interpreter.  When enabled, the sys module grows
-a new function:
-
-settscdump(bool)
-    If true, tell the Python interpreter to dump VM measurements to stderr.  If
-    false, turn off dump.  The measurements are based on the processor's
-    time-stamp counter.
-
-This build option requires a small amount of platform specific code.  Currently
-this code is present for linux/x86 and any PowerPC platform that uses GCC
-(i.e. OS X and linux/ppc).
-
-On the PowerPC the rate at which the time base register is incremented is not
-defined by the architecture specification, so you'll need to find the manual for
-your specific processor.  For the 750CX, 750CXe and 750FX (all sold as the G3)
-we find:
-
-    The time base counter is clocked at a frequency that is one-fourth that of
-    the bus clock.
-
-This build is enabled by the --with-tsc flag to configure.