From: "Jafa" <jafa@silicondust.com>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: FP vs SP
Date: Fri, 05 Sep 2003 23:08:00 -0000 [thread overview]
Message-ID: <004f01c37402$a6a6c610$0502a8c0@scenix.com> (raw)
In-Reply-To: <20030905230319.GA30712@nevyn.them.org>
Ah, I see it now - thanks!
Nick
----- Original Message -----
From: "Daniel Jacobowitz" <drow@mvista.com>
To: "Jafa" <jafa@silicondust.com>
Cc: <gdb@sources.redhat.com>
Sent: Friday, September 05, 2003 4:03 PM
Subject: Re: FP vs SP
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> On Fri, Sep 05, 2003 at 03:44:13PM -0700, Jafa wrote:
> > 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?
>
> You can control what GDB does here by defining a frame base method -
> see frame-base.h. Probably you've changed the meaning of
> get_frame_locals_address ().
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
>
>
prev parent reply other threads:[~2003-09-05 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 22:44 Jafa
2003-09-05 23:03 ` Daniel Jacobowitz
2003-09-05 23:08 ` Jafa [this message]
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='004f01c37402$a6a6c610$0502a8c0@scenix.com' \
--to=jafa@silicondust.com \
--cc=drow@mvista.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