From: Richard Henderson <rth@redhat.com>
To: "Petr Hluzín" <petr.hluzin@gmail.com>
Cc: Anitha Boyapati <anitha.boyapati@gmail.com>,
binutils@sourceware.org, gdb@sourceware.org,
GCC Patches <gcc-patches@gcc.gnu.org>,
chertykov@gmail.com, aesok@post.ru,
eric.weddington@atmel.com
Subject: Re: [avr] gas support for cfi info
Date: Thu, 17 Feb 2011 16:12:00 -0000 [thread overview]
Message-ID: <4D5D48E5.30404@redhat.com> (raw)
In-Reply-To: <AANLkTimf0+YtnhES6AZyY75zjYHu_Gkh_M+dJo4N7mUx@mail.gmail.com>
On 02/16/2011 02:47 PM, Petr HluzÃn wrote:
> What should I look for when testing?
Run the gdb testsuite with dwarf-3 enabled. Either by editing the
default in the compiler, or by some dejagnu argument that compiles
the tests with -gdwarf-3.
The use of Dwarf3 enables the use of DW_OP_call_frame_cfa in the
DW_AT_frame_base field, which means that the .debug_frame info will
be used every time local variables are referenced, as well as for
unwinding the stack.
If lots of tests fail, see if you can determine if the address
computed for the local variable -- or even more particularly a
function parameter -- is off by a byte. I have an idea that we're
missing a definition of
#define ARG_POINTER_CFA_OFFSET(FNDECL) -1
in GCC.
r~
next prev parent reply other threads:[~2011-02-17 16:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTim6hyXysiV-025BDgNJ84qaqTnkRdHi+e7bF2gx@mail.gmail.com>
[not found] ` <AANLkTi=Rnu-wb2W8FejN=XQHmHuTq7rZovKuDdO-QLwi@mail.gmail.com>
[not found] ` <AANLkTimOXF1V__SSFs1gtqJh5nc183EdeHm5NoeU6YXs@mail.gmail.com>
[not found] ` <AANLkTike2osnZS=sUphuN_=oFQLCDUs54uuGCWL6cLVQ@mail.gmail.com>
2011-02-15 17:41 ` Testing Call frame information in .debug_frame section Richard Henderson
2011-02-15 18:02 ` Richard Henderson
2011-02-15 22:13 ` Petr Hluzín
2011-02-16 16:51 ` Richard Henderson
2011-02-15 18:09 ` Anitha Boyapati
2011-02-15 18:48 ` Richard Henderson
2011-02-15 19:15 ` Anitha Boyapati
2011-02-15 19:03 ` [avr] gas support for cfi info Richard Henderson
2011-02-15 22:45 ` Petr Hluzín
2011-02-16 17:59 ` Richard Henderson
2011-02-16 22:49 ` Petr Hluzín
2011-02-17 16:12 ` Richard Henderson [this message]
2011-02-17 16:16 ` Tristan Gingold
2011-02-17 15:35 ` Anitha Boyapati
2011-02-17 16:05 ` Richard Henderson
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=4D5D48E5.30404@redhat.com \
--to=rth@redhat.com \
--cc=aesok@post.ru \
--cc=anitha.boyapati@gmail.com \
--cc=binutils@sourceware.org \
--cc=chertykov@gmail.com \
--cc=eric.weddington@atmel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=petr.hluzin@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).