memcpy.3: Change "should not overlap" to "must not overlap"

glibc 2.12 changed things so that applications that use memcpy() on
overlapping regions will encounter problems. (The standards have
long said that the behavious is undefined if the memory areas
overlap.)

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603144
In reference of http://lwn.net/Articles/414467/
and http://article.gmane.org/gmane.comp.lib.glibc.alpha/15278

Reported-by: Lars Wirzenius <liw@liw.fi>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2010-11-15 07:10:55 +01:00
parent 37a2356720
commit be78d88194
1 changed files with 2 additions and 2 deletions

View File

@ -25,7 +25,7 @@
.\" Lewine's _POSIX Programmer's Guide_ (O'Reilly & Associates, 1991)
.\" 386BSD man pages
.\" Modified Sun Jul 25 10:41:09 1993 by Rik Faith (faith@cs.unc.edu)
.TH MEMCPY 3 1993-04-10 "" "Linux Programmer's Manual"
.TH MEMCPY 3 2010-11-15 "" "Linux Programmer's Manual"
.SH NAME
memcpy \- copy memory area
.SH SYNOPSIS
@ -39,7 +39,7 @@ The
.BR memcpy ()
function copies \fIn\fP bytes from memory area
\fIsrc\fP to memory area \fIdest\fP.
The memory areas should not overlap.
The memory areas must not overlap.
Use
.BR memmove (3)
if the memory areas do overlap.