Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Nick Duffek <nsd@redhat.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: Possible remote.c patch for Z-packet breakpoints + Harvard + SID
Date: Tue, 17 Jul 2001 11:04:00 -0000	[thread overview]
Message-ID: <3B547E19.2070201@cygnus.com> (raw)
In-Reply-To: <200107162228.f6GMSNx20471@rtl.cygnus.com>

Nick,

Have you looked at ``TRANSLATE_XFER_ADDRESS''?  The d10v uses it to 
translate between a virtual CORE_ADDR and a real CORE_ADDR.

However, as a general rule, I think GDB should be consistent and always 
send down down CORE_ADDR's.  Remember the target needs to know about 
CORE_ADDRs anyway.  They are exactly the same as what BFD uses for 
bfd_vma's when specifying things like section addresses.

	Andrew


  reply	other threads:[~2001-07-17 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <o5pub0sqqy.fsf@toenail.toronto.redhat.com>
2001-07-16 15:28 ` Nick Duffek
2001-07-17 11:04   ` Andrew Cagney [this message]
2001-07-17 14:25     ` Nick Duffek
2001-07-18 13:47       ` 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=3B547E19.2070201@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.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