Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Florent DEFAY <spira.inhabitant@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: jeremy.bennett@embecosm.com,
	Anthony Berent <Anthony.Berent@arm.com>,
	gdb@sourceware.org
Subject: Re: new port
Date: Fri, 22 May 2009 12:24:00 -0000	[thread overview]
Message-ID: <8502af3c0905220524w71078d01kb4d95dc303775c2@mail.gmail.com> (raw)
In-Reply-To: <20090520141243.GE17566@adacore.com>

> This is related to your question above: You need to provide the value
> of the frame base, which apparently is the value of the SP at the time
> the function was entered.  It doesn't need to be the value of any given
> register.

That's true. This problem about 'next' is solved.
Thank you Joel.

I still wonder:
What should return target_frame_base_address? The base of the frame?
Even when it is not a given register?

Now I am facing another problem which was not before.
If I debug a simple program: main calls foo, I got trouble with frames.
In foo, the result of 'info frame' is:
_______________________________________________
Stack level 0, frame at 0x3fca:
 pc = 0x40 in add15 (main.c:8); saved pc 0x32a
 Outermost frame: unwinder did not report frame ID
 source language c.
 Arglist at 0x3fc4, args: a=25
 Locals at 0x3fc4, Previous frame's sp is 0x3fca
 Saved registers:
  pc at 0x3fca
_______________________________________________

What is shocking me is "Outermost frame: unwinder did not report frame ID"
and "Previous frame's sp" which has the same value as "frame at".

I would like to know which functions could be involved in these problems?

Regards.

Florent


  reply	other threads:[~2009-05-22 12:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 13:24 Florent DEFAY
2009-05-14 13:50 ` Hui Zhu
2009-05-14 14:05 ` Anthony Berent
2009-05-14 14:37   ` Jeremy Bennett
2009-05-20  8:26     ` Florent DEFAY
2009-05-20 14:12       ` Joel Brobecker
2009-05-22 12:24         ` Florent DEFAY [this message]
2009-05-22 14:43           ` Joel Brobecker
2009-05-25  7:17             ` Florent DEFAY
2009-05-25 14:59               ` Florent DEFAY
     [not found] ` <130942881126505163@unknownmsgid>
2009-05-14 14:46   ` Florent DEFAY
2009-05-14 16:46     ` Hui Zhu

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=8502af3c0905220524w71078d01kb4d95dc303775c2@mail.gmail.com \
    --to=spira.inhabitant@gmail.com \
    --cc=Anthony.Berent@arm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=jeremy.bennett@embecosm.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