mirror of
https://github.com/python/cpython.git
synced 2025-12-08 06:10:17 +00:00
cce38eefd4
Extend the documentation for disabling pymalloc with the `--without-pymalloc` flag regarding why it is worth to use it when enabling AddressSanitizer for Python build (which is done, e.g., in CPython's CI builds).
I have tested the CPython latest main build with both ASan and pymalloc enabled and it seems to work just fine. I did run the `python -m test` suite which didn't uncover any ASan crashes (though, it detected some memory leaks, which I believe are irrelevant here).
I have discussed ASan and this flag with @encukou on the CPython Core sprint on EuroPython 2025. We initially thought that the `--without-pymalloc` flag is needed for ASan builds due to the fact pymalloc must hit the begining of page when determining if the memory to be freed comes from pymalloc or was allocated by the system malloc. In other words, we thought, that ASan would crash CPython during free of big objects (allocated by system malloc). It may be that this was the case in the past, but it is not the case anymore as the `address_in_range` function used by pymalloc is annotated to be skipped from the ASan instrumentation.
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| android.rst | ||
| cmdline.rst | ||
| configure.rst | ||
| editors.rst | ||
| index.rst | ||
| ios.rst | ||
| mac.rst | ||
| mac_installer_01_introduction.png | ||
| mac_installer_02_readme.png | ||
| mac_installer_03_license.png | ||
| mac_installer_04_installation_type.png | ||
| mac_installer_05_custom_install.png | ||
| mac_installer_06_summary.png | ||
| mac_installer_07_applications.png | ||
| mac_installer_08_install_certificates.png | ||
| mac_installer_09_custom_install_free_threaded.png | ||
| unix.rst | ||
| win_install_freethreaded.png | ||
| win_installer.png | ||
| windows.rst | ||
