On 2010-06-13 11:58, Jonathan Nieder wrote: > Török Edwin wrote: > >> ==16452== Invalid read of size 8 >> ==16452== at 0x3A5E509DB2: ??? (strcpy.S:94) >> ... >> ==16452== Address 0x4fb63d0 is 0 bytes inside a block of size 7 alloc'd >> ==16452== at 0x4A061A7: malloc (vg_replace_malloc.c:195) >> ... >> >> And many more errors (most of them are strlen/__strcmp_sse3 repeated in >> various >> contexts): > > FYI: see http://bugs.debian.org/585051#17 > > Based on that, I suspect the proximate cause for the strlen + co false > positives is not glibc’s bumped version number but the new > --with-multi-arch feature.
Upgrading to the valgrind version in experimental (1:3.5.0+3.6.0svn20100609-1) makes all these warnings go away, if used with eglibc 2.11. However valgrind from experimental and eglibc 2.10 shows some new errors (again some uninitialized value/jump in dl_*), but I don't think thats relevant since unstable contains 2.11 now. Best regards, --Edwin -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
