From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cagney <ac131313@cygnus.com>
To: Nick Duffek <nsd@redhat.com>
Cc: insight@sources.redhat.com, gdb@sources.redhat.com, fnasser@redhat.com
Subject: Re: Register group proposal
Date: Wed, 21 Feb 2001 08:50:00 -0000
Message-id: <3A93F16C.E59D82AC@cygnus.com>
References: <200102210504.f1L54xJ01509@rtl.cygnus.com>
X-SW-Source: 2001-02/msg00276.html

Nick Duffek wrote:
> 
> On an architecture with a large register set, GDBtk's register window can
> be difficult to read and slow to update.  Users can customize the window
> to hide individual registers, but that's a tedious procedure.
> 
> Therefore, users would benefit from being able to switch easily between
> register subsets.
> 
> The CLI already provides two register subsets:
>   1. non-floating-point registers, displayed by "info registers";
>   2. all registers, displayed by "info all-registers".
> 
> This grouping is not as useful as it could be, for various reasons:

Nick,

Refering to the diagram:

> Actually, try this:
> 
>             context
>              /    \  .----.
>             /      \ |    |
>            /      frame---'
>           /       /   \
>    continuation  /     \
>         |       /       \
>         |      /         \
>         |   memcache   regcache
>         |      |           |
> ..........................................
>         |      |           |
>    targ-run  targ-mem  targ-regs

If I understand correctly, the methods you're describing would apply to
a ``frame''.  As the user moves up and down between frames, the
information provided by those methods could change.

Is that correct?

	Andrew