Eli,

Thanks for the review.

I think I addressed all of your comments, except one, which I will
reply to below.  You'll find 2 patches, a first one which just shows
the changes I made on top of the first patch, and then the second
one, which shows the new patch, in its entirety.  Hopefully this will
help you find quickly which changes were made, and verify that all
your comments have been addressed correctly.

> > +@table @code
> > +@kindex info partitions
> > +@item info partitions
> 
> Why not "info wtx partitions", or some other variant to make sure this
> is VxWorks specific?  "info partitions" is too general to reserve for
> a niche platform.

The reason why this hasn't been put under the "wtx" prefix is because
I don't consider partitions to be a VxWorks-specific concept.  I don't
know very much about the specifics, but I think that partitions are
defined by ARINC 653. But, beyond ARINC 653, I think that this concept
can be used in many areas, and we might find one day another platform
where the concept of partitions is used as well.

Right now, the implementation we have in GDB is ad hoc, and WTX calls
are hard-coded inside the partition support code.  However, my plan,
if I have the courage and enough rainy days, is to make that entirely
generic, so that the code can be shared with other platforms that might
come up which also provides a form of partition support.

I hope that answers your concerns.

Thanks,
-- 
Joel