memmove, memmove_s
Defined in header <string.h> | ||
---|---|---|
void* memmove( void* dest, const void* src, size_t count ); | (1) | |
errno_t memmove_s(void *dest, rsize_t destsz, const void *src, rsize_t count); | (2) | (since C11) |
count
characters from the object pointed to by src
to the object pointed to by dest
. Both objects are interpreted as arrays of unsigned char
. The objects may overlap: copying takes place as if the characters were copied to a temporary character array and then the characters were copied from the array to dest
.dest
or src
is a null pointer.[dest, dest+destsz)
(if both dest
and destsz
are valid) and calls the currently installed constraint handler function: -
dest
orsrc
is a null pointer -
destsz
orcount
is greater thanRSIZE_MAX
-
count
is greater thandestsz
(buffer overflow would occur)
dest
< count
<= destsz
; in other words, an erroneous value of destsz
does not expose the impending buffer overflow. As with all bounds-checked functions, memmove_s
is only guaranteed to be available if __STDC_LIB_EXT1__
is defined by the implementation and if the user defines __STDC_WANT_LIB_EXT1__
to the integer constant 1 before including string.h
.Parameters
dest | - | pointer to the object to copy to |
destsz | - | max number of bytes to modify in the destination (typically the size of the destination object) |
src | - | pointer to the object to copy from |
count | - | number of bytes to copy |
Return value
dest
dest
is not a null pointer and destsz
is valid, writes destsz
zero bytes in to the destination array.Notes
memmove
may be used to set the effective type of an object obtained by an allocation function.
Despite being specified "as if" a temporary buffer is used, actual implementations of this function do not incur the overhead or double copying or extra memory. A common approach (glibc and bsd libc) is to copy bytes forwards from the beginning of the buffer if the destination starts before the source, and backwards from the end otherwise, with a fall back to the more efficient memcpy
when there is no overlap at all.
Where strict aliasing prohibits examining the same memory as values of two different types, memmove
may be used to convert the values.
Example
#define __STDC_WANT_LIB_EXT1__ 1 #include <stdio.h> #include <stdint.h> #include <inttypes.h> #include <string.h> #include <stdlib.h> int main(void) { char str[] = "1234567890"; puts(str); memmove(str+4, str+3, 3); // copy from [4,5,6] to [5,6,7] puts(str); // setting effective type of allocated memory to be int int *p = malloc(3*sizeof(int)); // allocated memory has no effective type int arr[3] = {1,2,3}; memmove(p,arr,3*sizeof(int)); // allocated memory now has an effective type // reinterpreting data double d = 0.1; // int64_t n = *(int64_t*)(&d); // strict aliasing violation int64_t n; memmove(&n, &d, sizeof d); // OK printf("%a is %" PRIx64 " as an int64_t\n", d, n); #ifdef __STDC_LIB_EXT1__ set_constraint_handler_s(ignore_handler_s); char src[] = "aaaaaaaaaa"; char dst[] = "xyxyxyxyxy"; int r = memmove_s(dst,sizeof dst,src,5); printf("dst = \"%s\", r = %d\n", dst,r); r = memmove_s(dst,5,src,10); // count is greater than destsz printf("dst = \""); for(size_t ndx=0; ndx<sizeof dst; ++ndx) { char c = dst[ndx]; c ? printf("%c", c) : printf("\\0"); } printf("\", r = %d\n", r); #endif }
Possible output:
1234567890 1234456890 0x1.999999999999ap-4 is 3fb999999999999a as an int64_t dst = "aaaaayxyxy", r = 0 dst = "\0\0\0\0\0yxyxy", r = 22
References
- C11 standard (ISO/IEC 9899:2011):
- 7.24.2.2 The memmove function (p: 363)
- K.3.7.1.2 The memmove_s function (p: 615)
- C99 standard (ISO/IEC 9899:1999):
- 7.21.2.2 The memmove function (p: 326)
- C89/C90 standard (ISO/IEC 9899:1990):
- 4.11.2.2 The memmove function
See also
(C11) | copies one buffer to another (function) |
(C95)(C11) | copies a certain amount of wide characters between two, possibly overlapping, arrays (function) |
© cppreference.com
Licensed under the Creative Commons Attribution-ShareAlike Unported License v3.0.
http://en.cppreference.com/w/c/string/byte/memmove