Re: [PATCH 18/18] document the new VxWorks port

Joel Brobecker
2011-02-25T11:38:29Z

> > And what does "info threads" do on that target?
>
> It depends. In single-task mode, it displays only the thread being
> debugged. In multi-tasks mode, it displays the list of threads that
> have been created by a given kernel module.
>
> In both cases, "info threads" actually displays the threads that we
> are debugging (e.g. that are stopped when a breakpoint is reached);
> whereas "info wtx threads" displays any task running on kernel space
> (even those that that are not being debugged).

To expand a bit on what Jerome is saying, the reason we also do not
want to show all the threads that are not being debugged, is that
we do not want the user to attempt to switch to a thread that he is
currently not debugging.

--
Joel