Fix memory corruption introducted in FreeRTOS port (#556)
To remove compiler warning the valid core macro was modified to only check that the core passed in was < # of total cores. Unfortunately there are parts of the FreeRTOS code where the passed in core # is -1. The upstream catches this and returns FALSE, but my hacked version returned TRUE. This caused interesting memory corruption errors and crashes when the current task block[-1] was updated. Undo the change and fix the 1 spot where a warning happens instead. Undo the forced compiler -O0 for port.c, it was only masking the fault.
Showing
Please register or sign in to comment