From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Consistent format for memory addresses
Date: Wed, 25 May 2005 03:51:00 -0000 [thread overview]
Message-ID: <17043.63119.670138.172271@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050525033745.GA25868@nevyn.them.org>
> > However "info frame" gives:
> >
> > (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.
>
> I have no objection - but is it really that hard to treat it as a
> number?
In truth I don't mind seven or eight digits. What makes it difficult for me
is if the output of the CLI commands constantly change. I know the answer is
GDB/MI but I'm (still!) hoping to get one release of Emacs out using
annotations.
I don't know the logic behind the change in disassemble but my concern is that
it will mean that others like "info frame" will change at some unspecified
time in the future. I realise that I have to expect CLI output to move
forward, I'm just trying to ensure it happens in a co-ordinated manner.
Nick
next prev parent reply other threads:[~2005-05-25 3:51 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 [this message]
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
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=17043.63119.670138.172271@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.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