CareerCup

It's a security hazard if the passed destination string doesn't have null character ('\0') at the end. The iteration could continue indefinite till it see such a null character.

The strncpy could be used instead if we know how many bytes to copy.

Buffer overflow situation."Standard" solution to fixed it is to use the standard libraries calls.

instead, could use ctrncpy

strncpy, sorry

what strcpy does is copy the string character by character. a char size is 1 byte but usually the internal bus size is greater than 8 thus strcpy doesn't utilize complete bus.

In strcpy(p1,p2), if p1 and p2 overlap, there could be a problem. Memmove() solves this.

In strcpy(p1,p2), if p1 and p2 overlap, there could be a problem. Memmove() solves this.

also consider following example

char *p2 = "sachin";
     char *p1 = NULL;  
     strcpy(p1,p2); //segfault

     strcpy does not check for NULL pointers ;

Use strlcpy.
Look at its man page, it is different than strncpy.

The problem is that we should not overflow destination buffer. strlcpy does the copy upto destination buffer size and also guarantees null termination of destination.

There is no drawback. Blame the shooter, not the gun.

It is the programmer at fault if he cannot do proper bounds checking before using strcpy.