df75bbd536
Previously, if the target was halted before the FreeRTOS scheduler was started but after at least one thread was created, then the current thread would be set to whichever thread had the highest priority. In addition to being misleading, because that thread is not actually running, it can cause issues with gdb. For instance, breaking somewhere before the first thread is created will show the current execution as the current thread, but stepping over a line that creates a thread will cause the current thread to switch to the newly created thread and the current execution to disappear. The sudden disappearance of the current execution thread seems to confuse some versions of gdb. With this change, the value of xSchedulerRunning is checked to determine whether the scheduler has been started. If it hasn't, then a fake 'current execution' thread is always created and made the current thread. Signed-off-by: Frank Dischner <frank.dischner@gmail.com> Change-Id: Ide0fe7d9ffb9fac95cee4c805735f434c7c4934d Reviewed-on: https://review.openocd.org/c/openocd/+/6935 Tested-by: jenkins Reviewed-by: Asier Llano <asierllano@gmail.com> Reviewed-by: Tomas Vanek <vanekt@fbl.cz> |
||
---|---|---|
.. | ||
chibios.c | ||
chromium-ec.c | ||
eCos.c | ||
embKernel.c | ||
FreeRTOS.c | ||
hwthread.c | ||
linux_header.h | ||
linux.c | ||
Makefile.am | ||
mqx.c | ||
nuttx_header.h | ||
nuttx.c | ||
riot.c | ||
rtos_chibios_stackings.c | ||
rtos_chibios_stackings.h | ||
rtos_ecos_stackings.c | ||
rtos_ecos_stackings.h | ||
rtos_embkernel_stackings.c | ||
rtos_embkernel_stackings.h | ||
rtos_mqx_stackings.c | ||
rtos_mqx_stackings.h | ||
rtos_riot_stackings.c | ||
rtos_riot_stackings.h | ||
rtos_standard_stackings.c | ||
rtos_standard_stackings.h | ||
rtos_ucos_iii_stackings.c | ||
rtos_ucos_iii_stackings.h | ||
rtos.c | ||
rtos.h | ||
ThreadX.c | ||
uCOS-III.c | ||
zephyr.c |