You found the right threads to follow, and you're right that this is
lacking some documentation. (Patches/Writeups welcome.)
On Fri, Nov 1, 2019 at 10:18 AM Mathew Benson
wrote:
> "SHED" = scheduler_name, but that traces back to:
> name.name_u32 = _Thread_Scheduler_get_home( rtems_thread )-
"SHED" = scheduler_name, but that traces back to:
name.name_u32 = _Thread_Scheduler_get_home( rtems_thread )->name;
_Objects_Name_to_string(
name,
false,
canonical_task->scheduler_name,
sizeof( canonical_task->scheduler_name )
);
Shelve that one until later...
The task command doesn't appear to be defined there. I found the header in
libmisc/monitor/mon-task.c:rtems_monitor_task_dump_header(). It gets a
little buried in function callbacks from there. I'm trying to trace it
back now, but I recommend the documentation be improved to include what the
out
cpukit/libmisc/shell/ has many of the entry points for the shell functions.
On Fri, Nov 1, 2019 at 6:39 AM wrote:
> I take it that’s a no on the documentation. Can somebody just tell me
> what these mean or point me where in the code it is? It’s not an easy
> follow.
>
> Sent from my iPhone
>
I take it that’s a no on the documentation. Can somebody just tell me what
these mean or point me where in the code it is? It’s not an easy follow.
Sent from my iPhone
> On Oct 31, 2019, at 13:43, Mathew Benson wrote:
>
> is there any documentation that explains the actual output of the shel
is there any documentation that explains the actual output of the shell
commands? For example, the documentation for the task command says how to
run it, and gives the following sample output:
SHLL [/] # task
ID NAME SHED PRI STATE MODESEVENTS WAITINFO
-
