Glibc change exposing bugs
Posted Nov 10, 2010 21:20 UTC (Wed) by JoeBuck
In reply to: Glibc change exposing bugs
Parent article: Glibc change exposing bugs
No, the semantics of the function are that the behavior is not defined if the source and destination strings overlap, as the relevant standards and the man page clearly state. That's why there's an alternative function named memmove. If you write C, call memcpy, and the arguments overlap, you've written a non-portable program.
to post comments)