Stowage/cpython
2
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-11-03 23:21:29 +00:00
Code Issues Projects Releases Packages Wiki Activity

closes docs: remove references to Py_USING_MEMORY_DEBUGGER (GH-30284)

Browse source
This commit is contained in:
Carlos Damazio 2021-12-29 19:20:42 -03:00 • committed by GitHub
parent bc87ac6d0b
commit 8e11237c5d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

9
Misc/README.valgrind
View file

@ -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 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, are still two things you must do to suppress the warnings. First,
you must use a suppressions file. One is supplied in you must use a suppressions file. One is supplied in
Misc/valgrind-python.supp. Second, you must do one of the following: Misc/valgrind-python.supp. Second, you must uncomment the lines in
Misc/valgrind-python.supp that suppress the warnings for PyObject_Free and
* Uncomment Py_USING_MEMORY_DEBUGGER in Objects/obmalloc.c, PyObject_Realloc.
then rebuild Python
* 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 If you want to use Valgrind more effectively and catch even more
memory leaks, you will need to configure python --without-pymalloc. memory leaks, you will need to configure python --without-pymalloc.