Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Jafa" <jafa@silicondust.com>
To: <gdb@sources.redhat.com>
Subject: FP vs SP
Date: Fri, 05 Sep 2003 22:44:00 -0000	[thread overview]
Message-ID: <003301c373ff$3a923160$0502a8c0@scenix.com> (raw)

Hi all,

I recently updated the ip2k gdb port to use the new frame handling support
in gdb.

It can reliably do a stack backtrace and can reliably step-over etc.

The one problem is that all local variables show up as garbage.

I have looked into this and it seams that GDB is using the frame-pointer
(aka SP as at the entry point of the function) as the reference point for
the stack offset of the local variables. Is this correct or have I screwed
up something in my frame handling code?

Looking at the stabs information coming out of gcc (2.97) the offsets are
all specified as being relative to the nominal SP (stack pointer at the
start of any c-line)... is this correct or should it be giving FP relative
addresses?

I would appreciate any advice.

Thanks

Nick


             reply	other threads:[~2003-09-05 22:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-05 22:44 Jafa [this message]
2003-09-05 23:03 ` Daniel Jacobowitz
2003-09-05 23:08   ` Jafa

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='003301c373ff$3a923160$0502a8c0@scenix.com' \
    --to=jafa@silicondust.com \
    --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