public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: Harvard proposal
Date: Fri, 23 Feb 2001 20:27:00 -0000	[thread overview]
Message-ID: <m2k86g1yv8.fsf@kelso.bothner.com> (raw)
In-Reply-To: <3A970CE6.6B2D2F34@cygnus.com>

Andrew Cagney <ac131313@cygnus.com> writes:

> A CORE_ADDR is a cannonical address within the target address space.  A
> CORE_ADDR should, in theory, be able to identify every target byte (or
> if someone gets it working - word).

To clarify: By "target address space" do you mean the combined address
spaces of all the targets put together, or the address space of any
single target?  In other words, should a CORE_ADDR would also provide
some way of identifying a specific sub-space (i.e. specific target)?
Or should sub-space identification (which subsumes process id and host
network address) be something *separate* from the CORE_ADDR?

> However, as with traditional C, I'd suggest following the convention of
> CORE_ADDR (void*) for pointers and LONGEST (long) for offsets.

Again to clarify:  We're talking *target* void*, represented as an
integer type in gdb, not a pointer type.
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/~per/

  reply	other threads:[~2001-02-23 20:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-10 12:19 Nick Duffek
2001-02-10 13:27 ` Per Bothner
2001-02-10 17:11   ` Nick Duffek
2001-02-23 17:25   ` Andrew Cagney
2001-02-23 20:27     ` Per Bothner [this message]
2001-02-26  8:34       ` Andrew Cagney
2001-02-26  8:49         ` Per Bothner
2001-02-26 10:13           ` Andrew Cagney
2001-02-13 13:22 ` Andrew Cagney
2001-02-13 13:35   ` Nick Duffek

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=m2k86g1yv8.fsf@kelso.bothner.com \
    --to=per@bothner.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).