Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: Michael.Snyder@palmsource.com
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: [RFC] h8300 "info registers" fix
Date: Sat, 23 Sep 2006 01:08:00 -0000	[thread overview]
Message-ID: <200609230108.k8N18HNY019655@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <0F4DF2E21F33DD46BE7B8CDEEB0E16D307EAB4@ussunex01.palmsource.com> 	(Michael.Snyder@palmsource.com)

> Date: Wed, 13 Sep 2006 13:49:26 -0700
> From: "Michael Snyder" <Michael.Snyder@palmsource.com>
> 
> Daniel: 
> >On Wed, Sep 13, 2006 at 01:20:09PM -0700, Michael Snyder wrote:
> >> Grumble -- is the regcache kept in host order, or target order?
> >
> >Target order.
> >
> >[Which is apparently a bit weird; most debug interfaces I've seen
> >lately use host order.]
> 
> That's right -- it's a relic of the fact that the original 
> "register cache" was the register packet itself, which is 
> generated on the target side.  The target doesn't know anything
> about the host, so there's no way that can be in host order.
> 
> Anyway, in that case, the gdb_byte[4] approach is more likely
> to be correct, eh?

Yes, gdb_byte is the type we use for target byte buffers.

> I think I understand the problem now -- the pseudo-register is
> only one byte, so it's "natural" to call pseudo_register_read
> with a one byte buffer.  But the physical register is four bytes,
> so you have to have a four byte buffer to read it.
> 
> Wonder why it ever worked?   ;-/

The fact that almost all variables on a 32-bit machines are
word-aligned?

Mark


  reply	other threads:[~2006-09-23  1:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 15:05 Yoshinori Sato
2006-09-12 20:28 ` Michael Snyder
2006-09-13  2:28   ` Yoshinori Sato
2006-09-13 15:54 ` Yoshinori Sato
2006-09-13 20:05   ` Michael Snyder
2006-09-13 20:09     ` Daniel Jacobowitz
2006-09-13 20:23       ` Michael Snyder
2006-09-13 20:30         ` Daniel Jacobowitz
2006-09-13 20:59           ` Michael Snyder
2006-09-23  1:08             ` Mark Kettenis [this message]
2006-09-23  1:06           ` Mark Kettenis
2006-09-23  3:20             ` Jim Blandy
2006-09-23  3:26               ` Daniel Jacobowitz
2006-09-14  9:40     ` Yoshinori Sato
2006-09-19 16:28 ` Yoshinori Sato
2006-09-23 18:00   ` Mark Kettenis
2006-11-16  8:30     ` Yoshinori Sato

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=200609230108.k8N18HNY019655@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=Michael.Snyder@palmsource.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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