Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Anitha Boyapati <anitha.boyapati@gmail.com>
To: gdb@sourceware.org
Subject: Testing Call frame information in .debug_frame section
Date: Tue, 01 Feb 2011 13:04:00 -0000	[thread overview]
Message-ID: <AANLkTim6hyXysiV-025BDgNJ84qaqTnkRdHi+e7bF2gx@mail.gmail.com> (raw)

Hello,

I would like to use some help with regarding to call frame information
present in .debug_frame section in DWARF - 2.

+ Firstly, I understand that .debug_frame can be used to unwind the stack.
+ Secondly, I understand that .debug_frame is optional to gdb.
http://sourceware.org/gdb/papers/unwind.html

Now I am trying to fix a bug in AVR port of gcc to emit call-frame
information (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17994). The
problem is testing.

Initially, I thought avr-gdb can be used to backtrace/up/down with the
newly generated elf file (with a .debug_frame section in it). However,
avr-gdb does not seem to use this particular section. The version is
7.0.1. I am not sure how to test the FDEs in .debug_frame section
other than manual inspection. I am sort of newbie with DWARF-2. So, I
could be missing some pointers.

Can someone suggest a strategy? or better yet can someone shed
information on which features of  gdb uses .debug_frame section.

Thanks
Anitha


             reply	other threads:[~2011-02-01 13:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 13:04 Anitha Boyapati [this message]
2011-02-13  2:34 ` Petr Hluzín
2011-02-13  9:57   ` Anitha Boyapati
2011-02-13 15:11     ` Petr Hluzín
2011-02-15 17:41       ` 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
2011-02-17 16:16                   ` Tristan Gingold
2011-02-17 15:35               ` Anitha Boyapati
2011-02-17 16:05                 ` Richard Henderson
2011-02-17 19:53                   ` Richard Henderson
2011-02-22 16:18                     ` Anitha Boyapati
2011-02-22 17:51                       ` Richard Henderson
2011-02-15 18:18       ` Testing Call frame information in .debug_frame section Anitha Boyapati
2011-02-15 22:12         ` Petr Hluzín
2011-02-14 16:42     ` Tom Tromey
2011-02-14 22:43       ` Petr Hluzín
2011-02-15 15:06         ` 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=AANLkTim6hyXysiV-025BDgNJ84qaqTnkRdHi+e7bF2gx@mail.gmail.com \
    --to=anitha.boyapati@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