From aaeb2bd110b3df8df2f6a2f00eacba4b76b20a61 Mon Sep 17 00:00:00 2001 From: Jeroen Domburg Date: Tue, 25 Apr 2017 17:47:25 +0800 Subject: [PATCH] Assert when a new task is started on a nonexisting CPU --- components/freertos/tasks.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/components/freertos/tasks.c b/components/freertos/tasks.c index ff407d9baf..59974ef5e6 100644 --- a/components/freertos/tasks.c +++ b/components/freertos/tasks.c @@ -1044,6 +1044,11 @@ static void prvAddNewTaskToReadyList( TCB_t *pxNewTCB, TaskFunction_t pxTaskCode { TCB_t *curTCB, *tcb0, *tcb1; + /* Assure that xCoreID is valid or we'll have an out-of-bounds on pxCurrentTCB + You will assert here if e.g. you only have one CPU enabled in menuconfig and + are trying to start a task on core 1. */ + configASSERT( xCoreID == tskNO_AFFINITY || xCoreID < portNUM_PROCESSORS); + /* Ensure interrupts don't access the task lists while the lists are being updated. */ taskENTER_CRITICAL(&xTaskQueueMutex); -- 2.40.0