Paul Eggert wrote: > On 03/15/2012 05:04 AM, Jim Meyering wrote: >> I.e., can valgrind be taught that when a >> memmove call appears to read a few bytes beyond end of the source buffer, >> that it is ok, as long the overrun is consistent with the alignment of >> the source pointer? > > Sure, just fix valgrind; this should be easy since it supplies > its own memmove. See: > > https://bugzilla.redhat.com/show_bug.cgi?id=705790 > > which talks about just such a fix for Fedora 15. > > Hmm, but why are you seeing the problem in Fedora *17*? > Is that a regression? Or was there some problem with the fix?
Thanks. I've filed a BZ for valgrind (essentially copying my post): http://bugzilla.redhat.com/803802
