This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Testing Call frame information in .debug_frame section
- From: Anitha Boyapati <anitha dot boyapati at gmail dot com>
- To: gdb at sourceware dot org
- Date: Tue, 1 Feb 2011 18:33:58 +0530
- Subject: Testing Call frame information in .debug_frame section
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