Hi there,
Since upgrading to a new version of valgrind quite a while ago, valgrind
gets spammy, even with the Python suppressions in place. I suspect this
is because valgrind is getting more picky. I'm getting stuff like this:
==10199== Conditional jump or move depends on uninitialised value(s)
==10199== at 0x1B8F4FD1: (within /lib/ld-2.3.5.so)
==10199== by 0x1B8EA4AA: (within /lib/ld-2.3.5.so)
==10199== by 0x4111F18F: (within /lib/tls/libc-2.3.5.so)
==10199== by 0x1B8EF026: (within /lib/ld-2.3.5.so)
==10199== by 0x4111FB85: _dl_open (in /lib/tls/libc-2.3.5.so)
==10199== by 0x4118FD32: (within /lib/tls/libdl-2.3.5.so)
==10199== by 0x1B8EF026: (within /lib/ld-2.3.5.so)
==10199== by 0x41190486: (within /lib/tls/libdl-2.3.5.so)
==10199== by 0x4118FDB0: dlopen (in /lib/tls/libdl-2.3.5.so)
==10199== by 0x80DCE40: _PyImport_GetDynLoadFunc (in /usr/bin/python2.4)
==10199== by 0x80D2622: _PyImport_LoadDynamicModule (in
/usr/bin/python2.4)
==10199== by 0x80D223F: (within /usr/bin/python2.4)
and generally ld related output, presumably something to do with dynamic
linking. This makes it harder to pick out potentially real memory issues.
I'm wondering whether others get this same behavior with valgrind and
have it fixed, or whether everybody is stuck with it. I looked for newer
suppressions in the Python repository at some point, but couldn't find
it then.
My valgrind version is 3.0.1
Regards,
Martijn
