diff options
| author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2021-12-29 22:47:37 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-12-29 22:47:37 (GMT) |
| commit | 864caaabe4264798afd0e9fde0fc875c7208429d (patch) | |
| tree | 6f0a9ae9fe66d7fcc1ce66dbf93b2ec7137f9242 | |
| parent | aa056ed472e9d0a79ea21784f6f5171d12a13f85 (diff) | |
| download | cpython-864caaabe4264798afd0e9fde0fc875c7208429d.zip cpython-864caaabe4264798afd0e9fde0fc875c7208429d.tar.gz cpython-864caaabe4264798afd0e9fde0fc875c7208429d.tar.bz2 | |
closes docs: remove references to Py_USING_MEMORY_DEBUGGER (GH-30284)
(cherry picked from commit 8e11237c5d24e649b26cc928b52bc37f2fde9c7a)
Co-authored-by: Carlos Damazio <carlos.damazio@damazio.dev>
| -rw-r--r-- | Misc/README.valgrind | 9 |
1 files changed, 3 insertions, 6 deletions
diff --git a/Misc/README.valgrind b/Misc/README.valgrind index b483b2e..ee9bfdf 100644 --- a/Misc/README.valgrind +++ b/Misc/README.valgrind @@ -12,12 +12,9 @@ can be used to force the usage of the malloc() allocator of the C library. If you don't want to read about the details of using Valgrind, there are still two things you must do to suppress the warnings. First, you must use a suppressions file. One is supplied in -Misc/valgrind-python.supp. Second, you must do one of the following: - - * Uncomment Py_USING_MEMORY_DEBUGGER in Objects/obmalloc.c, - then rebuild Python - * Uncomment the lines in Misc/valgrind-python.supp that - suppress the warnings for PyObject_Free and PyObject_Realloc +Misc/valgrind-python.supp. Second, you must uncomment the lines in +Misc/valgrind-python.supp that suppress the warnings for PyObject_Free and +PyObject_Realloc. If you want to use Valgrind more effectively and catch even more memory leaks, you will need to configure python --without-pymalloc. |