[issue31494] Valgrind suppression file

2017-09-22 Thread Stefan Krah
Stefan Krah added the comment: Also, I don't think --with-pydebug works well with valgrind. It's either: 1) --with-pydebug 2) CFLAGS="-O0 -g" --with-valgrind 3) CFLAGS="-O0 -g" --without-pymalloc Combining 2) and 3) probably does not hurt, but is not necessary. -- resolution:

[issue31494] Valgrind suppression file

2017-09-22 Thread Stefan Krah
Stefan Krah added the comment: The suppressions are mainly for "invalid access" due to a gc trick. The primary goal is to be definitely-lost-clean. I would say it works as expected. -- nosy: +skrah ___ Python tracker

[issue31494] Valgrind suppression file

2017-09-22 Thread Terry J. Reedy
Terry J. Reedy added the comment: 3.5 only gets security fixes, and this does not seem to be a security issue. Please retest with 3.6 or 3.7. -- nosy: +terry.reedy ___ Python tracker

[issue31494] Valgrind suppression file

2017-09-16 Thread Aaron Michaux
New submission from Aaron Michaux: The file "Misc/valgrind-python.supp" doesn't work on Linux x64, running Python3.5.2, when configured as such: --with-pydebug --with-valgrind --without-pymalloc Running the interpreter echo "x = 1; print(x)" | valgrind --tool=memcheck --leak-check=full