I independently filed this bug upstream and then found this report when about to report it in Debian.
Upstream bug: http://savannah.gnu.org/bugs/index.php?29253 I used bcopy rather than memmove in the patch I submitted to upstream because that fitted with prevailing conventions in the function I was patching, otherwise it is identical. For me, this bug appears to be architecture specific - it affects amd64 not i386 - I conjecture this is due to differing optimized implementations in libc. Max. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
