POSIX Simulator: Assert if vPortYield called from a non-FreeRTOS thread #1247
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.
Assert if
vPortYield
called from a non-FreeRTOS threadDescription
As requested by @aggarg here I'm adding an assert to obviously crash if
vPortYield
gets called from a non-FreeRTOS thread. This avoids intermittent freezes depending on the state ofpxCurrentTCB
where FreeRTOS may suspend the non-FreeRTOS thread (and never un-suspend it). Instead, with this PR, the program crashes, making the underlying issue more easily findable & fixable.Test Steps
Call xTaskCreate outside of a FreeRTOS thread after the scheduler is started. Sometimes this will lead to the calling thread getting suspended forever.
Checklist:
Related Issue
#1237