On 08/12/2014 04:57 PM, William Brana wrote:
Can you run valgrind with debugging information? It might us tell us at
least which allocation is too short.
It could be a harmless over-read from the libc string functions
(particularly if valgrind has not been set up correctly on your system).
==43000== at 0x89019F3: XcursorScanTheme.part.0 (library.c:137)
From library.c:
137 full = malloc (strlen (dir) + 1 + strlen (subdir) + 1 +
strlen (file) + 1);
So this looks indeed like a strlen implementation (possibly inlined)
which is not properly instrumented.
--
Florian Weimer / Red Hat Product Security
