From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-38596-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 14049 invoked by alias); 1 Feb 2011 13:04:28 -0000
Received: (qmail 14041 invoked by uid 22791); 1 Feb 2011 13:04:27 -0000
X-SWARE-Spam-Status: No, hits=0.6 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Received: from mail-qw0-f41.google.com (HELO mail-qw0-f41.google.com) (209.85.216.41)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 01 Feb 2011 13:04:23 +0000
Received: by qwa26 with SMTP id 26so6454395qwa.0        for <gdb@sourceware.org>; Tue, 01 Feb 2011 05:04:22 -0800 (PST)
Received: by 10.229.235.147 with SMTP id kg19mr5194239qcb.61.1296565460079; Tue, 01 Feb 2011 05:04:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.83.209 with HTTP; Tue, 1 Feb 2011 05:03:58 -0800 (PST)
From: Anitha Boyapati <anitha.boyapati@gmail.com>
Date: Tue, 01 Feb 2011 13:04:00 -0000
Message-ID: <AANLkTim6hyXysiV-025BDgNJ84qaqTnkRdHi+e7bF2gx@mail.gmail.com>
Subject: Testing Call frame information in .debug_frame section
To: gdb@sourceware.org
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2011-02/txt/msg00001.txt.bz2

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