From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb@sources.redhat.com
Cc: nickrob@snap.net.nz
Subject: Re: info frame
Date: Mon, 17 Apr 2006 07:38:00 -0000 [thread overview]
Message-ID: <ubqv0zn6s.fsf@gnu.org> (raw)
In-Reply-To: <20060417013343.GA4114@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 16 Apr 2006 21:33:43 -0400)
> Date: Sun, 16 Apr 2006 21:33:43 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb@sources.redhat.com
>
> > >> 553^done,stack=[frame=
> > >> {level="0",addr="0x00003db0",fp="0xbffff2c0",......
> >
> > 0xbffff2c0 should not be the value of $fp but the value of "frame at..." in
> > 'info frame`?
>
> In fact, it's like that it will be the "frame at" address.
Daniel, I cannot parse this sentence, and consequently I cannot figure
out what are you saying in general.
> But I don't
> think it would be wise to architect that into the interface; I think I
> explained why earlier, but if not, it's because this is a touchy
> internal interface for GDB. If you want to display it to the user, you
> might want something different - either explicitly the $sp, or
> explictly the architectural $fp register, or explicitly the call frame
> address. If you want to use it in a frontend, then all we should offer
> is an opaque ID for equality testing, IMHO.
Are you saying that the "frame at ..." part in the CLI output is
meaningless for users? If so, why do we show it at all?
next prev parent reply other threads:[~2006-04-17 7:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 0:37 Nick Roberts
2006-04-17 1:33 ` Mark Kettenis
2006-04-17 5:54 ` Nick Roberts
2006-04-17 5:57 ` Daniel Jacobowitz
2006-04-17 6:37 ` Nick Roberts
2006-04-17 7:38 ` Eli Zaretskii [this message]
2006-04-17 8:41 ` Vladimir Prus
2006-04-17 14:01 ` Daniel Jacobowitz
2006-04-18 8:40 ` Eli Zaretskii
2006-04-17 7:35 ` Eli Zaretskii
2006-04-17 9:05 ` Mark Kettenis
2006-04-17 11:21 ` Eli Zaretskii
2006-04-17 12:16 ` Mark Kettenis
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=ubqv0zn6s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--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