From: Mitar <mmitar@gmail.com>
To: tromey@redhat.com
Cc: gdb@sourceware.org
Subject: Re: Custom call frame description
Date: Tue, 26 Jan 2010 08:31:00 -0000 [thread overview]
Message-ID: <f63c4b2d1001260030q69f12143m5eac936ac8b6c2df@mail.gmail.com> (raw)
In-Reply-To: <f63c4b2d1001250133u2b4f8b3fn608ebaf8a95daf07@mail.gmail.com>
Hi!
OK. I figured it out. Canonical frame address is top of the frame. So
where fp register is pointing in my case. I just forgot to describe in
DWARF that I save and where I save previous frame fp so this is the
reason why gdb could not unwind all frames on the stack.
> How can I specify where are function arguments? And locals?
I see that his is not stored in frame section but in subprogram entries.
Mitar
next prev parent reply other threads:[~2010-01-26 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 20:49 Mitar
2010-01-22 16:42 ` Tom Tromey
2010-01-25 9:33 ` Mitar
2010-01-26 8:31 ` Mitar [this message]
2010-01-27 15:23 ` Mitar
2010-01-27 15:58 ` Tom Tromey
2010-01-27 19:33 ` Mitar
2010-01-27 19:39 ` Daniel Jacobowitz
2010-01-27 21:07 ` Mitar
2010-01-27 19:39 ` Tom Tromey
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=f63c4b2d1001260030q69f12143m5eac936ac8b6c2df@mail.gmail.com \
--to=mmitar@gmail.com \
--cc=gdb@sourceware.org \
--cc=tromey@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