Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>
To: Nick Roberts <nickrob@snap.net.nz>, gdb@sources.redhat.com
Subject: Re: Consistent format for memory addresses
Date: Wed, 25 May 2005 05:27:00 -0000	[thread overview]
Message-ID: <7320911956265369@webhare> (raw)
In-Reply-To: <17043.61074.262608.156551@farnswood.snap.net.nz>

Nick Roberts <nickrob@snap.net.nz> wrote:

> (gdb) info frame
> Stack level 0, frame at 0xbffff730:
>  eip = 0x80484d9 in main (myprog.c:55); saved eip 0x4006015a
>        ^^^^^^^^^
>
> Still seven digits. The human mind adjusts easily to such differences, but
> front ends---or at least the one I'm writing for Emacs---don't.
>
> So that I don't have to keep making piecemeal changes, I suggest that
> memory addresses in "info frame" has the same format as disassemble
> and "info break". I've not looked at the internals but maybe they could
> all be printed with the same procedure call.
>
> WDYT?

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.

Cheers,

Mark



  parent reply	other threads:[~2005-05-25  5:27 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 [this message]
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=7320911956265369@webhare \
    --to=m.m.kettenis@alumnus.utwente.nl \
    --cc=gdb@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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