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

Eli Zaretskii
2011-02-25T11:38:45Z

> Date: Fri, 25 Feb 2011 12:26:47 +0100
> From: Jerome Guitton <guitton@adacore.com>
> Cc: brobecker@adacore.com, gdb-patches@sourceware.org
>
> > > 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?
>
> Well, the thing is that we have a sort of emulation of "processes"
> (I'd guess that the concept of "thread group" would actually be a
> better fit here) in multi-tasks mode. So we need to have a distinction
> between the threads that are of interest for the debugger and the ones
> that just happen to run on the same memory space.

The result looks like a bad UI to me, and requires a separate
command. But if that's what VxWorks users prefer, fine.