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

Jerome Guitton
2011-02-25T10:26:39Z

Thank you for your review. I'll let Joel give a complete response;
I'll just answer one of your questions:

> > +@kindex info wtx threads
> > +@item info wtx threads
>
> Why a separate command? Isn't it possible to use "info threads"?

"info threads" lists only the threads of the inferior, whereas
"info wtx threads" lists all threads on target. Typically, to attach
to one. It would be similar to "shell ps" on a native configuration.

The reason why it is not called, say, "info wtx processes", is a
particularity of VxWorks: most applications actually run on kernel
space, and share the same memory area. So they are really threads, not
processes.