anonymous wrote on Thursday, May 31, 2012:
This macro lets you set the len of the task’s name, but if you don’t want to use task names in your project (due to limited resources mainly), then you might set it to 1 (in order to include a least the null string terminator). However this approach is not true at all, 'cause if you check the Idle task it already has the name “Idle” and it is fixed!! (five chars). Under this escenario your TCBs are going to crash sooner or later because they aren’t allowing space for more than a one character, so critical data in the TCB will be overwritten.
There are two obvious workarounds:
1.- configMAX_TASK_NAME_LEN >5 or
2.- Hack the Idle task creation in order to change “Idle” to “”
None of them convince me so my question is: is it a bug or feature?