Task name IDLE not same as in the documentation (IDFGH-11021)

[Botond-Colop]

Answers checklist.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

Hello everyone,

I found a little difference between the documentation and the actual code.

According to the IDF Programming guide, two IDLEs task with different numbers should be started.

Otherwise, the task information cannot be requested from the operating system. (as you can see on this picture with IDLE)

The task list was queried with this function: vTaskList(taskList)
As we can see, the two IDLE tasks have the same name.
I am using IDF Version 4.4.2

What is also not optimal is that a task has a space Tmr Svc in its name instead of being separated by an underscore Tmr_Scv.

Thank you in advance.

Best regards,
Botond

[ESP-Marius]

Yeah, seems like this got changed back in a3c90bf during a freertos kernel upgrade.

We'll take a look at it!

[ammaree]

Can I second the comment on ‘Tmr Svc” becoming “TmrSvc” or similar. We use the task name as part of our Syslog support and a space in the name breaks the RFC standard!! Took the issue up with Richard Barry many years ago, he agreed to resolve but probably forgot…. On 23/09/07, 11:20, "ESP-Marius" ***@***.******@***.***>> wrote: Yeah, seems like this got changed back in a3c90bf<a3c90bf> during a freertos kernel upgrade. We'll take a look at it! — Reply to this email directly, view it on GitHub<#12204 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAYT7GDPXAISMJI34NYEMRDXZGGUXANCNFSM6AAAAAA4ORTFNE>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Botond-Colop]

The fact that the Tmr Svc has a space in the name is only a small problem, but the two "IDLE" tasks have the same name, in my opinion it is a bug.
With the same name "IDLE" you are not able to get some separately Task info to the two tasks. You can always query information about the last started task.

[igrr]

FWIW there is xTaskGetIdleTaskHandleForCPU which should allow you to get each of the idle task handles.