+- MISRA Discussion Forums (https://forum.misra.org.uk)
+-- Forum: MISRA C (https://forum.misra.org.uk/forumdisplay.php?fid=4)
+--- Forum: MISRA C:2012 and MISRA C:2023 guidelines (https://forum.misra.org.uk/forumdisplay.php?fid=21)
+---- Forum: 8.21 Standard libraries (https://forum.misra.org.uk/forumdisplay.php?fid=176)
+---- Thread: 21.18 is a safe strncpy function call non-compliant? (/showthread.php?tid=1650)
21.18 is a safe strncpy function call non-compliant? - dunno - 15-06-2023
I have a philosophical question.
Example code:
void foo() {
char buf[128];
strncpy(buf, "hello", 128);
}
The strncpy call does not have any undefined behavior. It will write "hello" in the buffer. Writing 6 bytes in a 128 byte buffer is not undefined behavior.
Does this code then violate rule 21.18? The third argument is larger than the size of the string literal.
Reading the amplification, it seems to me the code in non-compliant.
Reading the rationale, the point of this rule is to avoid buffer overflows. Since there is no buffer overflow does it mean the code is compliant?