➜

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 btharper, matrixise, vstinner
Date 2019-03-19.15:15:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1553008504.43.0.319690655451.issue36356@roundup.psfhosted.org>
In-reply-to
Content 
At least, "./python -V" no longer leaks at commit dcf617152e1d4c4a5e7965733928858a9c0936ca.

$ ./configure --with-valgrind
$ make
$ valgrind ./python -V
==9553== Memcheck, a memory error detector
==9553== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==9553== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==9553== Command: ./python -V
==9553== 
Python 3.8.0a2+
==9553== 
==9553== HEAP SUMMARY:
==9553==     in use at exit: 0 bytes in 0 blocks
==9553==   total heap usage: 33 allocs, 33 frees, 5,933 bytes allocated
==9553== 
==9553== All heap blocks were freed -- no leaks are possible
==9553== 
==9553== For counts of detected and suppressed errors, rerun with: -v
==9553== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
History
Date User Action Args
2019-03-19 15:15:04vstinnersetrecipients: + vstinner, matrixise, btharper
2019-03-19 15:15:04vstinnersetmessageid: <1553008504.43.0.319690655451.issue36356@roundup.psfhosted.org>
2019-03-19 15:15:04vstinnerlinkissue36356 messages
2019-03-19 15:15:04vstinnercreate