On Wed, May 04, 2011 at 12:10:48AM -0500, Jonathan Nieder wrote: > Sounds like http://sourceware.org/bugzilla/show_bug.cgi?id=12518 > which is fixed (sort of) by commit 0354e355 (2011-04-01).
Oh my word. So glibc 2.13 breaks random binaries that happened to incorrectly use memcpy() instead of memmove()? What's wrong with the glibc developers (and Ulrich Drepper in particular)? I'm with Linus on this: let's just revert to the old behaviour. A tiny amount of clock cycles saved isn't worth the instability. Thanks, -Steve P.S. I tried rebuilding glibc myself locally, but gcc also segfaults in the process :-(
signature.asc
Description: Digital signature
