[issue19893] Python cApi memory problem. Py_Initialize memory leak

2013-12-09 Thread STINNER Victor
Changes by STINNER Victor : -- resolution: -> invalid ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue19893] Python cApi memory problem. Py_Initialize memory leak

2013-12-09 Thread Roman
Roman added the comment: I've checked it one more time. And you're right (Sorry for trouble). I left old pyconfig.h in one place, so my new python compilation was not just what I wanted. Now I belive that everything with memory is ok. Thank you very much for your help. -- status: op

[issue19893] Python cApi memory problem. Py_Initialize memory leak

2013-12-08 Thread STINNER Victor
STINNER Victor added the comment: Sorry, but I still don't understand this issue. "Invalid read of size 4" is a known false positive. It can be worked around using ./configure --with-valgrind and the suppression list, or using ./configure --without-pymalloc. If you still get the warning, you u

[issue19893] Python cApi memory problem. Py_Initialize memory leak

2013-12-05 Thread Roman
Roman added the comment: I compiled python --with-valgrind --without-pymalloc, and used valgrind with suppressions. valgrind --suppressions=../Misc/valgrind-python.supp --leak-check=full --show-reachable=no --show-possibly-lost=no --track-origins=yes --log-file=vgrindNext.out ./test ---

[issue19893] Python cApi memory problem. Py_Initialize memory leak

2013-12-05 Thread STINNER Victor
STINNER Victor added the comment: You shoud configure --with-valgrind *and* use the suppression list, or disable pymalloc using configure. Victor -- ___ Python tracker ___ _

[issue19893] Python cApi memory problem. Py_Initialize memory leak

2013-12-05 Thread Roman
Roman added the comment: I've just done it. Python 3.3.3 --with-valgrind. I can't see the difference. Output appended. -- Added file: http://bugs.python.org/file32986/vgrind3.3.3vc.out ___ Python tracker _

[issue19893] Python cApi memory problem. Py_Initialize memory leak

2013-12-05 Thread Stefan Krah
Stefan Krah added the comment: Did you compile Python --with-valgrind? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue19893] Python cApi memory problem. Py_Initialize memory leak

2013-12-05 Thread Roman
Roman added the comment: I didn't use --suppressions=Misc/valgrind-python.supp before . (But I've done it now). Nothing important has changed. I understand that "possibly lost is not particularly informative". I'm rather worried about "Invalid read of size 4" etc. Isn't it potentially dangerou

[issue19893] Python cApi memory problem. Py_Initialize memory leak

2013-12-05 Thread Stefan Krah
Stefan Krah added the comment: Also, you have zero "definitely lost". "possibly lost" is not particularly informative in the context of running Python: These are almost certainly false positives. -- ___ Python tracker

[issue19893] Python cApi memory problem. Py_Initialize memory leak

2013-12-05 Thread Stefan Krah
Stefan Krah added the comment: Did you use --suppressions=Misc/valgrind-python.supp? -- ___ Python tracker ___ ___ Python-bugs-list ma

[issue19893] Python cApi memory problem. Py_Initialize memory leak

2013-12-05 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +haypo, skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue19893] Python cApi memory problem. Py_Initialize memory leak

2013-12-05 Thread Roman
New submission from Roman: I wrote small test program using Python cApi, and found some memory issues while working on it. I checked it with valgrind. (test code and valgrind output appended) Maybe I'm doing something wrong, but most of the problem occurs durring Py_Initialize. I've checked py