You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
k_thread_name_set(&context->rx_thread, "name");
-- or --
if (IS_ENABLED(CONFIG_THREAD_NAME)) {
char name[THREAD_MAX_NAME_LEN];
snprintk(name, sizeof(name), "name-%", <param>);
k_thread_name_set(ctx->rx_thread, name);
}
The text was updated successfully, but these errors were encountered:
GrygiriiS
changed the title
xenlib: internal threads doesn't have names which makes thread_analyzer output not inforamtive
xenlib: internal threads doesn't have names which makes thread_analyzer output not informative
May 9, 2024
The thread_analyzer produces output with thread addresses and no names, as result impossible to say which thread is where.
To Zephyr thread_analyzer enable use:
Thread names has to be added as:
The text was updated successfully, but these errors were encountered: