From: Nick Roberts <nickrob@snap.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: Consistent format for memory addresses
Date: Thu, 26 May 2005 04:12:00 -0000 [thread overview]
Message-ID: <17045.19722.540776.341861@farnswood.snap.net.nz> (raw)
In-Reply-To: <uu0kqy7so.fsf@gnu.org>
> > If you are saying that the address formats will only differ in their
> > number of leading zeros, and not in other ways, then that is good enough
> > for my purposes.
>
>
> Well, it's a number, right? What else can possibly change in the
> address format that leaves the numeric value unmodified? The only
> other thing, besides leading zeros, that I can think of is sign
> extension in some weird 32/64 bit situations. But that's a theory, I
> don't even know if it's possible in practice. So I'd say leading
> zeros is all you need to worry about for now.
If you're not constrained by knowledge of the internals of GDB like myself,
there are many possibilities. One command could start with a different
offset. It could work in the other direction. From the start or end of the
heap, the stack. It could be in octal, in decimal...
...but as you say, thats not the case.
Nick
next prev parent reply other threads:[~2005-05-26 4:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 3:18 Nick Roberts
2005-05-25 3:37 ` Daniel Jacobowitz
2005-05-25 3:51 ` Nick Roberts
2005-05-25 18:00 ` Eli Zaretskii
2005-05-25 21:10 ` Nick Roberts
2005-05-25 21:28 ` Daniel Jacobowitz
2005-05-25 23:11 ` Nick Roberts
2005-05-26 3:39 ` Eli Zaretskii
2005-05-26 3:46 ` Daniel Jacobowitz
2005-05-26 4:12 ` Nick Roberts [this message]
2005-05-25 4:12 ` Nick Roberts
2005-05-25 5:27 ` M.M. Kettenis
2005-05-25 5:48 ` Nick Roberts
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=17045.19722.540776.341861@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=eliz@gnu.org \
--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