Skip to content

Commit 8e11237

Browse files
author
Carlos Damazio
authored
closes docs: remove references to Py_USING_MEMORY_DEBUGGER (GH-30284)
1 parent bc87ac6 commit 8e11237

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

Misc/README.valgrind

+3-6
Original file line numberDiff line numberDiff line change
@@ -12,12 +12,9 @@ can be used to force the usage of the malloc() allocator of the C library.
1212
If you don't want to read about the details of using Valgrind, there
1313
are still two things you must do to suppress the warnings. First,
1414
you must use a suppressions file. One is supplied in
15-
Misc/valgrind-python.supp. Second, you must do one of the following:
16-
17-
* Uncomment Py_USING_MEMORY_DEBUGGER in Objects/obmalloc.c,
18-
then rebuild Python
19-
* Uncomment the lines in Misc/valgrind-python.supp that
20-
suppress the warnings for PyObject_Free and PyObject_Realloc
15+
Misc/valgrind-python.supp. Second, you must uncomment the lines in
16+
Misc/valgrind-python.supp that suppress the warnings for PyObject_Free and
17+
PyObject_Realloc.
2118

2219
If you want to use Valgrind more effectively and catch even more
2320
memory leaks, you will need to configure python --without-pymalloc.

0 commit comments

Comments
 (0)