Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@specifix.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Doug Evans <dje@sebabeach.org>, gdb@sourceware.org
Subject: Re: address space support
Date: Mon, 21 Apr 2008 19:25:00 -0000	[thread overview]
Message-ID: <1208800635.4615.88.camel@localhost.localdomain> (raw)
In-Reply-To: <20080420143205.GA24679@caradoc.them.org>

On Sun, 2008-04-20 at 10:32 -0400, Daniel Jacobowitz wrote:
> On Sat, Apr 19, 2008 at 09:38:26AM -0700, Doug Evans wrote:
> > But that's a ton of work, and not necessarily a maintainable way to go  
> > (the common case is addresses are just ints).  Hacking CORE_ADDR by  
> > putting the address space in the upper bits doesn't necessarily work 
> > either.
> 
> May not necessarily work but that's the state of the art.  All the
> targets with address spaces in GDB today have relatively small
> addressable areas so there are some bits to use.  And we use the same
> convention for CORE_ADDR that GNU binutils uses in the ELF symbol
> table, generally.
> 
> Also see "@code" and "@data", though there's nothing in the manual
> about them... TYPE_FLAG_CODE_SPACE and TYPE_FLAG_DATA_SPACE.

Erm, yeah -- those were something I did in 2001, when I was
at Red Hat.  See ChangeLog-2001.

I'd vaguely hoped that the work might be extensible to 
include general address spaces...

Sorry about the missing docs -- Eli, why didn't you 
catch me on that one?   ;-)




  reply	other threads:[~2008-04-21 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-20 10:11 Doug Evans
2008-04-21 17:19 ` Daniel Jacobowitz
2008-04-21 19:25   ` Michael Snyder [this message]
2008-04-22 20:07     ` Eli Zaretskii
2008-04-21 17:57 ` Ulrich Weigand

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=1208800635.4615.88.camel@localhost.localdomain \
    --to=msnyder@specifix.com \
    --cc=dje@sebabeach.org \
    --cc=drow@false.org \
    --cc=gdb@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