Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sources.redhat.com
Subject: Re: info frame
Date: Mon, 17 Apr 2006 05:54:00 -0000	[thread overview]
Message-ID: <17474.58179.83052.362944@farnswood.snap.net.nz> (raw)
In-Reply-To: <200604162333.k3GNXLeX004661@elgar.sibelius.xs4all.nl>


 ...
 > Note that while %ebp is usually used as a frame pointer register, the
 > architecture doesn't actually force you to do that.  Nowadays
 > compilers can and will generate frameless functions, and for those,
 > the value %ebp is meaningless.

Thanks for the explanation.  

Does this mean that if we choose to print the frame address in MI as part
of the output of -stack-list-frames:

>> Can somebody suggest the right fix? So far, I think that the simplest
>> approach is to make gdb print stack address of current frame, like  
>> is done
>> on the Apple branch:
>>
>>      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`?

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2006-04-17  0:37 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 [this message]
2006-04-17  5:57     ` Daniel Jacobowitz
2006-04-17  6:37       ` Nick Roberts
2006-04-17  7:38       ` Eli Zaretskii
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=17474.58179.83052.362944@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb@sources.redhat.com \
    --cc=mark.kettenis@xs4all.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