From: Nick Roberts <nickrob@snap.net.nz>
To: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>
Cc: gdb@sources.redhat.com
Subject: Re: Consistent format for memory addresses
Date: Wed, 25 May 2005 05:48:00 -0000 [thread overview]
Message-ID: <17044.4544.937299.451971@farnswood.snap.net.nz> (raw)
In-Reply-To: <7320911956265369@webhare>
> I'm all for consistency. But I think you should realize that pointers
> can be 64-bit too, or even 48-bit, so your code beter not depend on a
> fixed number of digits.
I've only got a 32 bit machine and AFAIK the output format of CLI commands
isn't precisely documented (why should it be, its for users, not frontends).
The disassembly view is only one part of the frontend and, I will have to rely
on bug reports to cover other architectures. For the moment, I'm just aiming
at damage limitation.
Nick
prev parent reply other threads:[~2005-05-25 5:48 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
2005-05-25 4:12 ` Nick Roberts
2005-05-25 5:27 ` M.M. Kettenis
2005-05-25 5:48 ` Nick Roberts [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=17044.4544.937299.451971@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sources.redhat.com \
--cc=m.m.kettenis@alumnus.utwente.nl \
/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).