Stefan Krah <stefan-use...@bytereef.org> added the comment: I'm getting a leak since this revision:
./configure --without-pymalloc CFLAGS="-O0 -g" && make valgrind --db-attach=yes --suppressions=./Misc/valgrind-python.supp --leak-check=full ./python leak.py ==32303== 16 bytes in 1 blocks are definitely lost in loss record 3 of 2,489 ==32303== at 0x4C27878: malloc (vg_replace_malloc.c:236) ==32303== by 0x41DDB0: PyMem_Malloc (object.c:1841) ==32303== by 0x4A72BF: vgetargskeywords (getargs.c:1432) ==32303== by 0x4A6E1C: PyArg_ParseTupleAndKeywords (getargs.c:1301) ==32303== by 0x55D1C8: float_new (floatobject.c:1557) ==32303== by 0x42B643: type_call (typeobject.c:708) ==32303== by 0x532A9F: PyObject_Call (abstract.c:2150) ==32303== by 0x491483: do_call (ceval.c:4260) ==32303== by 0x490A33: call_function (ceval.c:4063) ==32303== by 0x48BD49: PyEval_EvalFrameEx (ceval.c:2662) ==32303== by 0x48EA11: PyEval_EvalCodeEx (ceval.c:3414) ==32303== by 0x482FC6: PyEval_EvalCode (ceval.c:771) ---------- nosy: +skrah status: closed -> open _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14325> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
