summaryrefslogtreecommitdiff
path: root/man3/strcpy.3
blob: f2d18fe9780572f5e5e8c60985f3daa90653be4a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
.\" Copyright (C) 1993 David Metcalfe (david@prism.demon.co.uk)
.\"
.\" Permission is granted to make and distribute verbatim copies of this
.\" manual provided the copyright notice and this permission notice are
.\" preserved on all copies.
.\"
.\" Permission is granted to copy and distribute modified versions of this
.\" manual under the conditions for verbatim copying, provided that the
.\" entire resulting derived work is distributed under the terms of a
.\" permission notice identical to this one.
.\"
.\" Since the Linux kernel and libraries are constantly changing, this
.\" manual page may be incorrect or out-of-date.  The author(s) assume no
.\" responsibility for errors or omissions, or for damages resulting from
.\" the use of the information contained herein.  The author(s) may not
.\" have taken the same level of care in the production of this manual,
.\" which is licensed free of charge, as they might when working
.\" professionally.
.\"
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\"
.\" References consulted:
.\"     Linux libc source code
.\"     Lewine's _POSIX Programmer's Guide_ (O'Reilly & Associates, 1991)
.\"     386BSD man pages
.\" Modified Sat Jul 24 18:06:49 1993 by Rik Faith (faith@cs.unc.edu)
.\" Modified Fri Aug 25 23:17:51 1995 by Andries Brouwer (aeb@cwi.nl)
.\" Modified Wed Dec 18 00:47:18 1996 by Andries Brouwer (aeb@cwi.nl)
.\" 2007-06-15, Marc Boyer <marc.boyer@enseeiht.fr> + mtk
.\"     Improve discussion of strncpy().
.\"
.TH STRCPY 3  2007-06-15 "GNU" "Linux Programmer's Manual"
.SH NAME
strcpy, strncpy \- copy a string
.SH SYNOPSIS
.nf
.B #include <string.h>
.sp
.BI "char *strcpy(char *" dest ", const char *" src );
.sp
.BI "char *strncpy(char *" dest ", const char *" src ", size_t " n );
.fi
.SH DESCRIPTION
The
.BR strcpy ()
function copies the string pointed to by \fIsrc\fP,
including the terminating null byte ('\\0'),
to the buffer pointed to by \fIdest\fP.
The strings may not overlap, and the destination string
\fIdest\fP must be large enough to receive the copy.
.PP
The
.BR strncpy ()
function is similar, except that at most
\fIn\fP bytes of \fIsrc\fP are copied.
.BR Warning :
If there is no null byte
among the first \fIn\fP bytes of \fIsrc\fP,
the string placed in \fIdest\fP will not be null terminated.
.PP
If the length of
.I src
is less than
.IR n ,
.BR strncpy ()
pads the remainder of
.I dest
with null bytes.
.PP
A simple implementation of
.BR strncpy ()
might be:
.in +0.25i
.nf

char*
strncpy(char *dest, const char *src, size_t n){
    size_t i;

    for (i = 0 ; i < n && src[i] != '\\0' ; i++)
        dest[i] = src[i];
    for ( ; i < n ; i++)
        dest[i] = '\\0';

    return dest;
}
.fi
.in
.SH "RETURN VALUE"
The
.BR strcpy ()
and
.BR strncpy ()
functions return a pointer to
the destination string \fIdest\fP.
.SH "CONFORMING TO"
SVr4, 4.3BSD, C89, C99.
.SH NOTES
Some programmers consider
.BR strncpy ()
to be inefficient and error prone.
If the programmer knows (i.e., includes code to test!)
that the size of \fIdest\fP is greater than
the length of \fIsrc\fP, then
.BR strcpy ()
can be used.

If there is no terminating null byte in the first \fIn\fP
characters of \fIsrc\fP,
.BR strncpy ()
produces an unterminated string in \fIdest\fP.
Programmers often prevent this mistake by forcing termination
as follows:
.in +0.25i
.nf

strncpy(buf, str, n);
if (n > 0)
    buf[n - 1]= '\\0';
.fi
.in
.SH BUGS
If the destination string of a
.BR strcpy ()
is not large enough
(that is, if the programmer was stupid or lazy, and failed to check
the size before copying) then anything might happen.
Overflowing fixed length strings is a favorite cracker technique.
.SH "SEE ALSO"
.BR bcopy (3),
.BR memccpy (3),
.BR memcpy (3),
.BR memmove (3),
.BR wcscpy (3),
.BR wcsncpy (3)