From: kceiwH <kceiwh@gmail.com>
To: gdb@sourceware.org
Subject: Re: How and When a frame is constructed
Date: Wed, 05 Aug 2009 14:22:00 -0000 [thread overview]
Message-ID: <CE1D8CB2-30B0-4A22-9544-72F464008466@gmail.com> (raw)
In-Reply-To: <614D83AC-2659-4D60-8309-196D0EDE8050@gmail.com>
And I wonder if I know the values of all registers, could I construct
a frame from those values?
Regards,
Mao
On Aug 5, 2009, at 9:44 AM, kceiwH wrote:
> Hi,
>
> When I read GDB source codes, I don't understand how a frame is
> constructed, and when.
> As far as I know, get_current_frame is used to get a current frame.
> When current_frame is NULL, it will construct a sentinel_frame and
> unwind it to get current_frame. But I don't know where current_frame
> will be updated except get_current_frame. The
>
> I also guess that the frame stack will be updated when the inferior
> is running, stepped. But I still don't find the code to update the
> frame stack.
>
> I'm wondering when the first frame is constructed and pushed to
> frame stack and how to push to and pop from frame stack.
>
> Thanks in advance.
>
> Best Wishes,
>
> Mao
prev parent reply other threads:[~2009-08-05 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 13:45 kceiwH
2009-08-05 14:22 ` kceiwH [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=CE1D8CB2-30B0-4A22-9544-72F464008466@gmail.com \
--to=kceiwh@gmail.com \
--cc=gdb@sourceware.org \
/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