From: Andrew Cagney <ac131313@cygnus.com>
To: Nick Duffek <nsd@redhat.com>,
insight@sources.redhat.com, gdb@sources.redhat.com,
fnasser@redhat.com
Subject: Re: Register group proposal
Date: Wed, 21 Feb 2001 11:43:00 -0000 [thread overview]
Message-ID: <3A9419DB.6C3DA172@cygnus.com> (raw)
In-Reply-To: <3A93F16C.E59D82AC@cygnus.com>
Andrew Cagney wrote:
>
> 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,
Hmm, to expand a little:
> > Actually, try this:
> >
> > context
> > / \ .----.
> > / \ | |
> > / frame---'
> > / / \
> > continuation / \
> > | / \
> > | / \
> > | memcache regcache
> > | | |
> > ..........................................
> > | | |
> > targ-run targ-mem targ-regs
I think this interface is bound to the ``frame''. It is the frame, and
not regcache, that determines the current architecture. With that in
mind, I suspect that the implementation would end up looking like:
frame.h:
some date *****gimi_register_groups_for_frame (struct frame_info *);
where you might have:
frame.c:
some data *****
gimi_register_groups_for_frame (struct_frame_info *frame)
{
return gimi_gdbarch_register_groups_for_frame (frame->arch, frame?,
...???);
}
Given that at present a frame doesn't have an architecture (instead
there is a hardwired default) an intermediate version could just use the
default - ``current_gdbarch''.
The main points are that:
o core-gdb doesn't try to access
gdbarch directly - instead it
asks the frame what it thinks.
o the information isn't in someway
bound to the raw byte register
cache.
Andrew
next prev parent reply other threads:[~2001-02-21 11:43 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 20:56 Nick Duffek
2001-02-21 6:44 ` Fernando Nasser
2001-02-21 7:10 ` Nick Duffek
2001-02-21 7:36 ` Fernando Nasser
2001-02-21 7:58 ` Keith Seitz
2001-02-21 8:50 ` Andrew Cagney
2001-02-21 11:43 ` Andrew Cagney [this message]
2001-02-25 15:36 ` Nick Duffek
2001-02-21 11:43 ` Andrew Cagney
2001-02-21 12:28 ` Andrew Cagney
2001-02-21 12:18 ` Andrew Cagney
2001-02-22 0:59 ` Eli Zaretskii
2001-02-22 4:29 ` Nick Duffek
2001-02-22 8:46 ` Andrew Cagney
2001-02-22 8:56 ` Keith Seitz
2001-02-22 9:20 ` Andrew Cagney
2001-02-22 5:17 ` Nick Duffek
2001-02-22 6:36 ` Fernando Nasser
2001-02-22 8:23 ` Andrew Cagney
2001-02-22 7:58 ` Andrew Cagney
2001-02-22 8:37 ` Nick Duffek
2001-02-22 9:12 ` Andrew Cagney
2001-02-22 10:15 ` Nick Duffek
2001-02-22 10:25 ` Andrew Cagney
2001-02-22 11:40 ` Eli Zaretskii
2001-02-22 11:02 ` Kevin Buettner
2001-02-22 12:08 ` Andrew Cagney
2001-02-22 8:16 ` Andrew Cagney
2001-02-21 3:00 Stephane Carrez
2001-02-21 7:00 ` Nick Duffek
2001-02-21 9:34 ` Andrew Cagney
2001-02-22 9:19 Michael Elizabeth Chastain
2001-02-23 2:52 Bernard Dautrevaux
2001-02-24 15:43 ` Nick Duffek
2001-02-26 18:21 ` Andrew Cagney
2001-02-27 10:30 ` Jim Kleck
2001-02-27 11:24 ` Per Bothner
2001-02-27 13:44 ` Jim Kleck
2001-02-27 15:17 ` Andrew Cagney
2001-02-26 5:29 Bernard Dautrevaux
2001-02-26 9:28 ` Christopher Faylor
2001-02-26 10:56 ` Andrew Cagney
2001-02-26 11:28 ` Christopher Faylor
2001-02-26 17:02 ` Andrew Cagney
2001-02-27 8:53 ` Christopher Faylor
2001-02-27 9:57 ` Andrew Cagney
2001-02-28 1:59 Bernard Dautrevaux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A9419DB.6C3DA172@cygnus.com \
--to=ac131313@cygnus.com \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=insight@sources.redhat.com \
--cc=nsd@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).