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

Eli Zaretskii
2011-02-25T11:12:31Z

> Date: Fri, 25 Feb 2011 11:26:24 +0100
> From: Jerome Guitton <guitton@adacore.com>
> Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
>
>
> 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.

Since there's no "inferior" on this target, is it so bad to show all
the threads?

And what does "info threads" do on that target?

> 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.

That's fine, but then why not treat them as threads?