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 mmokrejs
Recipients mmokrejs, skrah, tim.peters
Date 2013-08-30.14:23:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Moreover, it should explain what that really does. One could think of several answers or even their combinations what this configure flag will really do:

a) python will run itself under valgrind, don't bother ever doing it yourself
b) you don't have to bother with uncommenting the lines in valgrind.supp
c) "make install" will install the valgrind.supp but you have to edit it on your own
d) you may use valgrind but don't use other tool replacing malloc(), like electric fence, DUMA, etc. You should be quite verbose how (in)compatible is this with other tools.

Or some combination of them?

valgrind docs say it won't work if a binary lacks debug symbols (wasn't compiled with -g). Initially I got mislead I though I have to convert my to blah.c using cython, compile that with "gcc -ggdb blah.c" and then I may run valgrind on the binary.

In the end, I don't understand why everybody has to remove the comment symbols from the valgrind-python.supp file at all. Why isn't that by default enabled?

I also suggest you mention right in the file other handy information because people quite likely get on this path while chasing memory corruption issues, maybe broken hardware:

1. Mention that python uses 256kB chunks by default.
2. Mention there exists --without-pymalloc as Tim explained me in
3. Explain how to interpret those stacktraces one could get:

Thank you!
Date User Action Args
2013-08-30 14:23:22mmokrejssetrecipients: + mmokrejs, tim.peters, skrah
2013-08-30 14:23:22mmokrejssetmessageid: <>
2013-08-30 14:23:22mmokrejslinkissue18859 messages
2013-08-30 14:23:22mmokrejscreate