From: Doug Evans <dje@sebabeach.org>
To: gdb@sourceware.org
Subject: address space support
Date: Sun, 20 Apr 2008 10:11:00 -0000 [thread overview]
Message-ID: <480A2002.9050405@sebabeach.org> (raw)
At Transmeta we had a hack to implement address spaces. I.e.,
CORE_ADDR isn't enough to fully describe all the bits of "memory" one
might want to examine. One could do things like "x/x
<addr-space-name>:<address>". Using that we also hacked in support for
x86 segments, so one could do "x/x fs:1234".
We didn't want to maintain a ton of local mods so we took a minimalist
route. Other ways that have been discussed in the past are things like
turning CORE_ADDR into a struct:
typedef struct { int address_space ; OLD_CORE_ADDR address; } NEW_CORE_ADDR;
or some such (appropriately typed, named, etc.).
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.
So I don't have a specific proposal, I'm just taking a survey of where
things have left off.
next reply other threads:[~2008-04-19 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 10:11 Doug Evans [this message]
2008-04-21 17:19 ` Daniel Jacobowitz
2008-04-21 19:25 ` Michael Snyder
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=480A2002.9050405@sebabeach.org \
--to=dje@sebabeach.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