From: Andrew Cagney <ac131313@cygnus.com>
To: Nick Duffek <nsd@redhat.com>
Cc: cagney@cygnus.com, fche@redhat.com, gdb-patches@sourceware.cygnus.com
Subject: Re: Possible remote.c patch for Z-packet breakpoints + Harvard + SID
Date: Wed, 18 Jul 2001 13:47:00 -0000 [thread overview]
Message-ID: <3B55F5D8.1060302@cygnus.com> (raw)
In-Reply-To: <200107171937.f6HJb4v24007@rtl.cygnus.com>
>>However, as a general rule, I think GDB should be consistent and always send
>>down down CORE_ADDR's.
>
>
> Meaning virtual CORE_ADDRs? I agree.
Yes.
> On 16-Jul-2001, Frank Ch . Eigler wrote:
>
>
>>If this gdb-side approach is not deemed acceptable to gdb folks, we
>>may be able to make complementary changes on the sid side without too
>>much littering.
>
>
> Do we have a consensus that a SID-side approach is preferable to a
> GDB-side one?
Looks like it (no one else has spoken up).
It means that GDB sends the remote target a CORE_ADDR and that the
remote target needs to provide a mechanism for mapping between the
hardware registers and a CORE_ADDR address. Not unlike
gdbarch->{read,write}_pc().
Andrew
prev parent reply other threads:[~2001-07-18 13:47 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
2001-07-17 14:25 ` Nick Duffek
2001-07-18 13:47 ` Andrew Cagney [this message]
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=3B55F5D8.1060302@cygnus.com \
--to=ac131313@cygnus.com \
--cc=cagney@cygnus.com \
--cc=fche@redhat.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