MISRA C:2012 Rule 19.1
An object shall not be assigned or copied to an overlapping object
Description
Rule Definition
An object shall not be assigned or copied to an overlapping object1 .
Rationale
When you assign an object to another object with overlapping memory, the behavior is undefined. The exceptions are:
You assign an object to another object with exactly overlapping memory and compatible type.
You copy one object to another using
memmove
.
Additional Message in Report
An object shall not be assigned or copied to an overlapping object.
Destination and source of XX overlap, the behavior is undefined.
Troubleshooting
If you expect a rule violation but do not see it, refer to Diagnose Why Coding Standard Violations Do Not Appear as Expected.
Examples
Check Information
Group: Overlapping Storage |
Category: Mandatory |
AGC Category: Mandatory |
Version History
Introduced in R2014bSee Also
1 All MISRA coding rules and directives are © Copyright The MISRA Consortium Limited 2021.
The MISRA coding standards referenced in the Polyspace® Bug Finder™ documentation are from the following MISRA standards:
MISRA C:2004
MISRA C:2012
MISRA C:2023
MISRA C++:2008
MISRA C++:2023
MISRA and MISRA C are registered trademarks of The MISRA Consortium Limited 2021.