Why not name this "regression in glibc causes memory corruption"? That's actually what is happening, and the solution is to either:
1) Fix glibc so the old behavior is not broken (mapping memcpy to memmove) 2) Downgrade glibc until it's fixed upstream
The fact that this regression has only been seen on proprietary code is irrelevant, it might be happening all over the place.
Why not name this "regression in glibc causes memory corruption"? That's actually what is happening, and the solution is to either:
1) Fix glibc so the old behavior is not broken (mapping memcpy to memmove)
2) Downgrade glibc until it's fixed upstream
The fact that this regression has only been seen on proprietary code is irrelevant, it might be happening all over the place.