This is the mail archive of the insight@sources.redhat.com mailing list for the Insight project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Register group proposal


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]