Public bug reported: I run 'valgrind python </dev/null' and get numerous memory access errors from valgrind. E.g.:
$ valgrind --suppressions=/usr/lib/valgrind/python.supp python ==23585== Memcheck, a memory error detector ==23585== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==23585== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==23585== Command: python ==23585== ==23585== Invalid read of size 4 ==23585== at 0x5740EF: PyObject_Free (in /usr/bin/python2.7) ==23585== by 0x45B9A6: code_dealloc.9725 (in /usr/bin/python2.7) ==23585== by 0x55F6EF: load_source_module.39052 (in /usr/bin/python2.7) ==23585== by 0x5600CA: import_submodule.39106 (in /usr/bin/python2.7) ==23585== by 0x4A0892: load_next.39111 (in /usr/bin/python2.7) ==23585== by 0x560963: import_module_level.isra.3.39132 (in /usr/bin/python2.7) ==23585== by 0x553EAA: builtin___import__.32787 (in /usr/bin/python2.7) ==23585== by 0x4BF2A5: PyObject_Call (in /usr/bin/python2.7) ==23585== by 0x4BF5A5: PyEval_CallObjectWithKeywords (in /usr/bin/python2.7) ==23585== by 0x46870A: PyEval_EvalFrameEx (in /usr/bin/python2.7) ==23585== by 0x57BD01: PyEval_EvalCodeEx (in /usr/bin/python2.7) ==23585== by 0x57CDA7: PyImport_ExecCodeModuleEx (in /usr/bin/python2.7) ==23585== Address 0x6694020 is 0 bytes inside a block of size 568 free'd ==23585== at 0x4C2A82E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==23585== by 0x6010814: fclose@@GLIBC_2.2.5 (iofclose.c:88) ==23585== by 0x55F683: load_source_module.39052 (in /usr/bin/python2.7) ==23585== by 0x5600CA: import_submodule.39106 (in /usr/bin/python2.7) ==23585== by 0x4A0892: load_next.39111 (in /usr/bin/python2.7) ==23585== by 0x560963: import_module_level.isra.3.39132 (in /usr/bin/python2.7) ==23585== by 0x553EAA: builtin___import__.32787 (in /usr/bin/python2.7) ==23585== by 0x4BF2A5: PyObject_Call (in /usr/bin/python2.7) ==23585== by 0x4BF5A5: PyEval_CallObjectWithKeywords (in /usr/bin/python2.7) ==23585== by 0x46870A: PyEval_EvalFrameEx (in /usr/bin/python2.7) ==23585== by 0x57BD01: PyEval_EvalCodeEx (in /usr/bin/python2.7) ==23585== by 0x57CDA7: PyImport_ExecCodeModuleEx (in /usr/bin/python2.7) ==23585== It is not a false positive of subtle low-level memory access of python as it is an invalid access from glibc's function, not a python internal function. The full valgrind output is uploaded here: http://paste.ubuntu.com/6166481/ ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python 2.7.3-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.2.0-54.82-generic 3.2.50 Uname: Linux 3.2.0-54-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 CheckboxSubmission: 8cd6ce4bf8fb309ce25728059c2cc919 CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3 Date: Sat Sep 28 15:48:47 2013 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: python-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232435 Title: 'valgrind python' shows numerous free'd memory accesses during initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1232435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
