Re: info frame

Eli Zaretskii
2006-04-17T14:01:34Z

> Date: Mon, 17 Apr 2006 08:26:06 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb@sources.redhat.com,
> nickrob@snap.net.nz
>
> On Mon, Apr 17, 2006 at 10:16:43AM +0300, Eli Zaretskii wrote:
> > > 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.
>
> Replace like with likely and it has slightly more intelligible grammar.

It does, thanks.

> > 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?
>
> It isn't completely meaningless. However, it's highly system specific,

Mark seemed to say something different: that it's quite consistent.

If it has no well-defined meaning, perhaps we should move it to some
maint command.