Il giorno ven, 11/02/2011 alle 10.55 +0100, Michael Haubenwallner ha scritto: > > what do you think of working around the memcpy troubles with > glibc-2.13 by > simply redirecting memcpy to memmove within glibc, either > unconditionally or > optional/temporary (via USE-flag?) until everyone uses memmove where > necessary?
That unless things start crashing down nobody will fix the issues at all. We're not talking a last minute change! memcpy() *always* documented not to use overlapping memory areas. -- Diego Elio Pettenò — Flameeyes http://blog.flameeyes.eu/
