(In reply to comment #8) > "Buggy" code can be linked to the new memcpy@@GLIBC_2.14 by just recompiling, > no? That doesn't really solve anything.
It solves everything. If you just relink without retesting you're an idiot and acting irresponsible.
(In reply to comment #8)
> "Buggy" code can be linked to the new memcpy@@GLIBC_2.14 by just recompiling,
> no? That doesn't really solve anything.
It solves everything. If you just relink without retesting you're an idiot and acting irresponsible.