From: Andrew Cagney <ac131313@redhat.com>
To: gdb@sources.redhat.com
Subject: multiple frame/register caches (or what isn't in GDB 6)
Date: Fri, 06 Jun 2003 20:02:00 -0000 [thread overview]
Message-ID: <3EE0F343.70807@redhat.com> (raw)
Since GDB 6 is looming large, its probably time to think about what to
not try and squeese into that release.
While the on-going architectural changes have many potential benefits,
one more immediate and tangable addition is per-thread frame/register
caches.
At present, when the user switches threads, GDB discards all local state
(register cache, all frames, ...). The plan is for GDB to instead
maintain per-thread register/frame caches that are only flushed when the
target changes. For GUI environments, which like to switch between and
display lots of threads, this should be a very big win.
Anyway, to give this an update. The architecture methods are now
[almost] all parameterized with an explicit frame/regcache, and that
makes the addition of multiple active register/frame caches to core GDB
just that much easier - the problem of architecture specific code
indirectly manipulating global state is eliminated (see read_pc_pid).
The remaining obvious problems are of course read_pc_pid, and the target
side supply_register.
So, don't expect this in GDB 6 :-)
enjoy,
Andrew
reply other threads:[~2003-06-06 20:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3EE0F343.70807@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.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).