Are the Python developers running Python under Valgrind? If not, FYI, Valgrind is a excellent memory-checker for Linux. Valgrind is reporting a ton of memory problems. Worrisome are "Conditional jump or move depends on uninitialised value(s)" errors. I simply started the Python 2.4.2 interpreter, then Ctrl+D, on Linux Fedora 5.
........ ==2923== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al. ==2923== Using LibVEX rev 1471, a library for dynamic binary translation. ==2923== Copyright (C) 2004-2005, and GNU GPL'd, by OpenWorks LLP. ==2923== Using valgrind-3.1.0, a dynamic binary instrumentation framework. ==2923== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al. ==2923== For more details, rerun with: -v ==2923== ==2923== My PID = 2923, parent PID = 2922. Prog and args are: ==2923== /usr/bin/python ==2923== ==2923== Conditional jump or move depends on uninitialised value(s) ==2923== at 0x331BD6096B: PyObject_Free (in /usr/lib64/libpython2.4.so.1.0) ==2923== by 0x331BD5BFE9: (within /usr/lib64/libpython2.4.so.1.0) ==2923== by 0x331BD6555E: PyString_InternInPlace (in /usr/lib64/libpython2.4.so.1.0) ==2923== by 0x331BD69C6E: PyString_InternFromString (in /usr/lib64/libpython2.4.so.1.0) ==2923== by 0x331BD7053C: (within /usr/lib64/libpython2.4.so.1.0) ==2923== by 0x331BD7549F: PyType_Ready (in /usr/lib64/libpython2.4.so.1.0) ==2923== by 0x331BD76F6E: PyType_Ready (in /usr/lib64/libpython2.4.so.1.0) ==2923== by 0x331BD5E42F: _Py_ReadyTypes (in /usr/lib64/libpython2.4.so.1.0) ==2923== by 0x331BDB3E6A: Py_InitializeEx (in /usr/lib64/libpython2.4.so.1.0) ==2923== by 0x331BDB910D: Py_Main (in /usr/lib64/libpython2.4.so.1.0) ==2923== by 0x331181D083: __libc_start_main (in /lib64/libc-2.4.so) ==2923== [..] -- http://mail.python.org/mailman/listinfo/python-list
