Can someone suggest the cause of this warning?
Should I file a bug? Against python or glibc?
This is python code being valgrind-ed on x86_64.
The suppressions file here:
http://svn.python.org/projects/python/trunk/Misc/
is installed, and additional suppressions for Memcheck:Value8 and
Memcheck:Addr8
have been added in PyObject_Free and PyObject_Realloc.
As a side node, why is this suppressions file not installed by default?
==16039== Conditional jump or move depends on uninitialised value(s)
==16039== at 0x37E2EDBBED: __strcpy_chk (in /lib64/libc-2.3.90.so)
==16039== by 0x3B9D79F3CB: (within /usr/lib64/libpython2.4.so.1.0)
==16039== by 0x3B9D7A1A2F: (within /usr/lib64/libpython2.4.so.1.0)
==16039== by 0x3B9D7A1DEF: (within /usr/lib64/libpython2.4.so.1.0)
==16039== by 0x3B9D7A1FA6: PyImport_ImportModuleEx (in
/usr/lib64/libpython2.4.so.1.0)
==16039== by 0x3B9D784CFF: (within /usr/lib64/libpython2.4.so.1.0)
==16039== by 0x3B9D735E25: PyObject_Call (in
/usr/lib64/libpython2.4.so.1.0)
==16039== by 0x3B9D787760: PyEval_CallObjectWithKeywords (in
/usr/lib64/libpython2.4.so.1.0)
==16039== by 0x3B9D78A1D2: PyEval_EvalFrame (in
/usr/lib64/libpython2.4.so.1.0)
==16039== by 0x3B9D78D701: PyEval_EvalCodeEx (in
/usr/lib64/libpython2.4.so.1.0)
==16039== by 0x3B9D78D753: PyEval_EvalCode (in
/usr/lib64/libpython2.4.so.1.0)
==16039== by 0x3B9D7A06B4: PyImport_ExecCodeModuleEx (in
/usr/lib64/libpython2.4.so.1.0)
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
