From: Tom Horsley <horsley1953@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb@sourceware.org
Subject: Re: How does gdb deal with bizarre frame descriptions?
Date: Thu, 20 May 2010 00:21:00 -0000 [thread overview]
Message-ID: <20100519202147.4de59642@zooty> (raw)
In-Reply-To: <201005191842.00180.vapier@gentoo.org>
On Wed, 19 May 2010 18:41:59 -0400
Mike Frysinger wrote:
> look at the frames sections of the gdb internals manual as it describes the
> algorithms gdb uses (or rather, the framework gdb has that each arch/port
> extends).
>
> you can also use 'set debug frame 1' to get more insight on the frame
> construction.
Thanks for the pointers, but I think I have discovered that the
compiler is actually generating correct, but ridiculous frame info.
The code really is using ebp as a frame register, but it also
has stored a copy of the frame pointer on the stack and described
that saved copy in the dwarf instead of just using ebp+offset
like all the code it generated actually does. I have no clue
why it does that :-).
prev parent reply other threads:[~2010-05-20 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 20:06 Tom Horsley
2010-05-19 22:42 ` Mike Frysinger
2010-05-20 0:21 ` Tom Horsley [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=20100519202147.4de59642@zooty \
--to=horsley1953@gmail.com \
--cc=gdb@sourceware.org \
--cc=vapier@gentoo.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