calling prvCheckTasksWaitingTermination

wildcard98 wrote on Monday, April 21, 2008:

iam trying to restart a task in my app. First i delete the task and then i create a new one of this type. I know that the idle task will clean up the memory, but what if the idle-task can not run anytime.
What could go wrong if i call prvCheckTasksWaitingTermination(…) right after deleting the task manually from a user-level "control" task?
In my App unfortunatly the idle task is always starved of microcontroller processing time :frowning:

Thank you.

rtel wrote on Wednesday, April 23, 2008:

I don’t see a problem with this, although I should remove the call from the idle task to ensure there are no conflicts with both your task and the idle task accessing the data structures at the same time.  You would also have to make prvCheckTasksWaitingTermination() public, rather than static.

Search the forum for other solutions to this.  There was a discussion within the last month or two.