Fix one typical misusage of CMock. #1112
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
CMock has three policies when dealing with pointer:
By default, CMock use compare_data policy.
Most test cases in FreeRTOS need to compare the pointer itself, and we haven't use CMock properly.
For example, one test case of vTaskResume is wrong, and because CMock compares the data pointed by pointer currently, so the error didn't exposed.
There are so many misusage need to fix, it will take a lot of work. I'm here to fix one typical misusage first.
Test Steps
Checklist:
Related Issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.