That's what symbol versioning is all about.
Posted Nov 10, 2010 23:03 UTC (Wed) by khim
In reply to: Glibc change exposing bugs
Parent article: Glibc change exposing bugs
GLibC does have such mechanism: it's called ELF symbol versioning. But the policy does not cover cases similar to discussed one: if it's bug in a program (and the fact that regions must not intersect is well-documented one... heck, it's reason for memmove(3) existence), then there will be no new version of function.
The question of "do we actually want such change" is separate issue.
to post comments)