bpo-18859: Document --with-valgrind option in README.valgrind (#10591)
This commit is contained in:
parent
8b9c33ea9c
commit
d5d33681c1
|
@ -2,6 +2,10 @@ This document describes some caveats about the use of Valgrind with
|
|||
Python. Valgrind is used periodically by Python developers to try
|
||||
to ensure there are no memory leaks or invalid memory reads/writes.
|
||||
|
||||
If you want to enable valgrind support in Python, you will need to
|
||||
configure Python --with-valgrind option or an older option
|
||||
--without-pymalloc.
|
||||
|
||||
UPDATE: Python 3.6 now supports PYTHONMALLOC=malloc environment variable which
|
||||
can be used to force the usage of the malloc() allocator of the C library.
|
||||
|
||||
|
@ -46,6 +50,10 @@ If you disable PyMalloc, most of the information in this document and
|
|||
the supplied suppressions file will not be useful. As discussed above,
|
||||
disabling PyMalloc can catch more problems.
|
||||
|
||||
PyMalloc uses 256KB chunks of memory, so it can't detect anything
|
||||
wrong within these blocks. For that reason, compiling Python
|
||||
--without-pymalloc usually increases the usefulness of other tools.
|
||||
|
||||
If you use valgrind on a default build of Python, you will see
|
||||
many errors like:
|
||||
|
||||
|
|
Loading…
Reference in New Issue