Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: powerpc remote target registers
Date: Wed, 03 Dec 2003 04:23:00 -0000	[thread overview]
Message-ID: <3FCD6527.9000506@gnu.org> (raw)
In-Reply-To: <3FCC21B2.30000@eCosCentric.com>


> But then the registers aren't marked as cached at all, so they're now requested from the target each time you do "info all-registers", even though they come up with 0s. Should I pretend the registers not supplied by the target were 0, or should I mark them as unavailable (i.e. the same as what having an "x" does) so at least it's consistent?

Ah, they should be supplied but with a value of zero.  The protocol (for 
  historic reasons) specifies that a short G packet should have the 
missing entries treated as zero (like you intended).

Andrew


  reply	other threads:[~2003-12-03  4:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-29  2:07 Jonathan Larmour
2003-12-01 18:52 ` Andrew Cagney
2003-12-02  5:23   ` Jonathan Larmour
2003-12-03  4:23     ` Andrew Cagney [this message]
2003-12-04  7:32       ` Jonathan Larmour
2003-12-04 15:11         ` Andrew Cagney
2003-12-06 22:08           ` Jonathan Larmour
2003-12-06 22:58             ` Andrew Cagney

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=3FCD6527.9000506@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jifl@eCosCentric.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