StringCbCopyA function (strsafe.h)
Copies one string to another. The size of the destination buffer is provided to the function to ensure that it does not write past the end of this buffer.
StringCbCopy is a replacement for the following functions:
STRSAFEAPI StringCbCopyA( [out] STRSAFE_LPSTR pszDest, [in] size_t cbDest, [in] STRSAFE_LPCSTR pszSrc );
The destination buffer, which receives the copied string.
The size of the destination buffer, in bytes. This value must consider the length of pszSrc plus the terminating null character. The maximum number of bytes allowed is
STRSAFE_MAX_CCH * sizeof(TCHAR).
A pointer to a buffer containing the source string. This source string must be null-terminated.
||Source data was present, fully copied without truncation, and the resultant destination buffer is null-terminated.|
The value in cbDest is either less than
||The copy operation failed due to insufficient buffer space. The destination buffer contains a truncated, null-terminated version of the intended result. In situations where truncation is acceptable, this may not necessarily be seen as a failure condition.|
Note that this function returns an HRESULT value, unlike the functions that it replaces.
Compared to the functions it replaces, StringCbCopy provides additional processing for proper buffer handling in your code. Poor buffer handling is implicated in many security issues that involve buffer overruns. StringCbCopy always null-terminates and never overflows a valid destination buffer, even if the contents of the source string change during the operation.
Behavior is undefined if the strings pointed to by pszSrc and pszDest overlap.
Neither pszSrc nor pszDest should be NULL. See StringCbCopyEx if you require the handling of null string pointer values.
StringCbCopy can be used in its generic form, or in its more specific forms. The data type of the string determines the form of this function that you should use.
|String Data Type||String Literal||Function|
The strsafe.h header defines StringCbCopy as an alias which automatically selects the ANSI or Unicode version of this function based on the definition of the UNICODE preprocessor constant. Mixing usage of the encoding-neutral alias with code that not encoding-neutral can lead to mismatches that result in compilation or runtime errors. For more information, see Conventions for Function Prototypes.
|Minimum supported client||Windows XP with SP2 [desktop apps | UWP apps]|
|Minimum supported server||Windows Server 2003 with SP1 [desktop apps | UWP apps]|