diff options
| author | Victor Stinner <vstinner@redhat.com> | 2018-12-03 11:29:29 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-12-03 11:29:29 (GMT) |
| commit | c275be54411d425c90e7c679ddb5321ba458f61d (patch) | |
| tree | cb6180265d9b933064d9565c69b1f71659f80d1f /Python/pythonrun.c | |
| parent | dfd4a1d8414ea54a3c56e909167983a503e51067 (diff) | |
| download | cpython-c275be54411d425c90e7c679ddb5321ba458f61d.zip cpython-c275be54411d425c90e7c679ddb5321ba458f61d.tar.gz cpython-c275be54411d425c90e7c679ddb5321ba458f61d.tar.bz2 | |
bpo-35368: Make PyMem_Malloc() thread-safe in debug mode (GH-10828)
When Python is compiled in debug mode, PyMem_Malloc() uses debug
hooks, but it also uses pymalloc allocator instead of malloc().
Problem: pymalloc is not thread-safe, whereas PyMem_Malloc() is
thread-safe in release mode (it's a thin wrapper to malloc() in this
case).
Modify the debug hook to use malloc() for PyMem_Malloc().
Diffstat (limited to 'Python/pythonrun.c')
0 files changed, 0 insertions, 0 deletions