[Python-Dev] python vs. valgrind
Neal D. Becker
ndbecker2 at verizon.net
Mon Aug 30 19:08:33 CEST 2004
I just tried running valgrind-2.1.2 on python-2.3.3.
[nbecker at rpppc1 ~]$ valgrind --tool=memcheck /usr/bin/python ./Hello.py
==12284== Memcheck, a memory error detector for x86-linux.
==12284== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward et al.
==12284== Using valgrind-2.1.2, a program supervision framework for
x86-linux.
==12284== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward et al.
==12284== For more details, rerun with: -v
==12284==
==12284== Conditional jump or move depends on uninitialised value(s)
==12284== at 0x807AFA4: PyObject_Free (in /usr/bin/python)
==12284== by 0x8074A4F: (within /usr/bin/python)
==12284== by 0x8082AF0: PyString_InternInPlace (in /usr/bin/python)
==12284== by 0x8082BA2: PyString_InternFromString (in /usr/bin/python)
==12284==
==12284== Use of uninitialised value of size 4
==12284== at 0x807AFB2: PyObject_Free (in /usr/bin/python)
==12284== by 0x8074A4F: (within /usr/bin/python)
==12284== by 0x8082AF0: PyString_InternInPlace (in /usr/bin/python)
==12284== by 0x8082BA2: PyString_InternFromString (in /usr/bin/python)
[many, many more complaints...]
Does this indicate a problem?
More information about the Python-Dev
mailing list