fix(FreeRTOS): Initialize uxTaskNumber at task initialization (IDFGH-1815) #4025
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.
uxTaskNumber
member ofstruct tskTaskControlBlock
is not initialized at thread creation.As the TCB can be dynamically allocated,
uxTaskNumber
might then get a value from the heap.As a result, the user might get a seems-valid value when calling
uxTaskGetTaskNumber()
and then take wrong decisions.This fix zeroes
uxTaskNumber
when the task is initialized.