From: Andrew Cagney <ac131313@cygnus.com>
To: Mark Kettenis <kettenis@wins.uva.nl>
Cc: gdb@sources.redhat.com, eliz@delorie.com
Subject: Re: Register cache
Date: Tue, 13 Feb 2001 13:38:00 -0000 [thread overview]
Message-ID: <3A89991B.805A4A44@cygnus.com> (raw)
In-Reply-To: <200102102237.f1AMbnJ00230@delius.kettenis.local>
> Is this really a good idea? I think it is, at least on targets where
> getting at the registers is relatively expensive since it involves a
> system call. Therefore I propose to make this "official" and change
> the comment on target_fetch_registers() to:
>
> /* Fetch at least register REGNO, or all regs if REGNO == -1. */
This behavour is pretty much engrained in GDB so yes, the documentation
should be changed to reflect this.
> Another question is whether we should make this behaviour (I mean
> having target_fetch_registers() supply all registers it managed to get
> in one go) recommended practice.
I'd agree with Nick and not go that far. Keep the contract between
GDB's core and the target simple.
Andrew
next prev parent reply other threads:[~2001-02-13 13:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-10 14:37 Mark Kettenis
2001-02-11 12:07 ` Nick Duffek
2001-02-11 23:26 ` Eli Zaretskii
2001-02-12 9:46 ` Nick Duffek
2001-02-12 10:37 ` Eli Zaretskii
2001-02-16 15:21 ` Mark Kettenis
2001-02-17 0:28 ` Eli Zaretskii
2001-02-17 3:19 ` Mark Kettenis
2001-02-13 13:38 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-31 5:50 Register Cache Peter Reilley
2000-08-24 17:01 Wrong PC after external interrupt Fabrice Gautier
2000-08-29 18:01 ` Register Cache Steven Johnson
2000-08-30 21:40 ` Steven Johnson
2001-03-26 6:46 ` Andrew Cagney
2001-03-26 7:22 ` Fernando Nasser
[not found] ` <3ABFD062.17EDADAF@neurizon.net>
2001-03-29 16:27 ` Andrew Cagney
2001-03-29 16:27 ` Fernando Nasser
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=3A89991B.805A4A44@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@delorie.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@wins.uva.nl \
/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).