How to resolve polyspace MISRA C:2012 D4.14 rule when am passing pointer as parameter to function ?

Question

sai akshay 2019-9-11

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/479913-how-to-resolve-polyspace-misra-c-2012-d4-14-rule-when-am-passing-pointer-as-parameter-to-function

回答： Luke Halberstadt 2019-12-26

this is my fuction FCM_CopyDTCStatusByDTCNumber (uint32 DTC_Number, uint8* data_ptr) and for this its throwing

MISRA C:2012 D4.14 (Required)

The validity of values received from external sources shall be checked.

Array index is from an unsecure source. Index may be negative or too big

and am checking pointer is not null as

void FCM_CopyDTCStatusByDTCNumber (uint32 DTC_Number, uint8* data_ptr)

{

uint16 DTC_Index;

/* Find the DTC Index */

DTC_Index = FCM_FindDTCIndex(DTC_Number);

/* Loop till the all DTCs */

if (DTC_Index < FCM_MAXNUM_DTCS)

{

if(data_ptr!= NULL_PTR) <------

{

/* Copy the DTC Number to buffer */

*data_ptr++ = (uint8)(FCM_DTCInfo[DTC_Index].Fault_Id >> FCM_SIXTEEN);

*data_ptr++ = (uint8)(FCM_DTCInfo[DTC_Index].Fault_Id >> FCM_EIGHT);

*data_ptr++ = (uint8)(FCM_DTCInfo[DTC_Index].Fault_Id);

}

check the arrow mark IN ABOVE CODE i will resolve pointer is not NULL

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Luke Halberstadt 2019-12-26

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/479913-how-to-resolve-polyspace-misra-c-2012-d4-14-rule-when-am-passing-pointer-as-parameter-to-function#answer_407813

Even though you are checking that the input parameter is not NULL, it is still possible for the dereferenced "data_ptr" to traverse beyond the end of the valid allocated memory.

Please note that verifying whether or not you stay within the bounds of the provided memory cannot be checked within "FCM_CopyDTCStatusByDTCNumber" unless broader context is given. This could be in the form of the code that calls this function or you could use external constraints:

https://www.mathworks.com/help/releases/R2019b/bugfinder/ug/specify-constraints.html

As described on the constraint page, you cannot constrain function inputs when using Bug Finder. This means that even after you provide constraints for the memory pointed to by "data_ptr", you will still see 4.14 violations in Bug Finder and will need to justify these via comments.

Code Prover ignores directive 4.14, so it will never show 4.14 violations, but it does check for valid memory access, taking constraints into account.

MISRA Checkers:

https://www.mathworks.com/help/releases/R2019b/bugfinder/ug/polyspace-misra-c-2012-checker.html

Code Prover Run-Time Error Memory Check:

https://www.mathworks.com/help/releases/R2019b/codeprover/static-memory-checks.html