This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients lemburg, serhiy.storchaka, vstinner
Date 2016-03-09.11:50:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1457524247.21.0.660791172709.issue26516@psf.upfronthosting.co.za>
In-reply-to
Content
The motivation to support PYTHONMALLOC=malloc (always use malloc) and not just PYTHONMALLOC=debug (enable debug hooks) is to allow to use external memory debugger like Valgrind.

Valgrind doesn't like pymalloc (pymalloc raises false alarms), we had to a configuration option for it: ./configure --with-valgrind.

Using PYTHONMALLOC=malloc allows to use Valgrind on the system Python, it's easier to use. No need to recompile Python.
History
Date User Action Args
2016-03-09 11:50:47vstinnersetrecipients: + vstinner, lemburg, serhiy.storchaka
2016-03-09 11:50:47vstinnersetmessageid: <1457524247.21.0.660791172709.issue26516@psf.upfronthosting.co.za>
2016-03-09 11:50:47vstinnerlinkissue26516 messages
2016-03-09 11:50:46vstinnercreate