From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31691 invoked by alias); 15 Feb 2011 17:41:14 -0000 Received: (qmail 31674 invoked by uid 22791); 15 Feb 2011 17:41:13 -0000 X-SWARE-Spam-Status: No, hits=-5.0 required=5.0 tests=AWL,BAYES_00,FSL_RU_URL,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 15 Feb 2011 17:41:09 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p1FHf6W0020420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 15 Feb 2011 12:41:06 -0500 Received: from anchor.twiddle.home (ovpn-113-82.phx2.redhat.com [10.3.113.82]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p1FHf6L9008798; Tue, 15 Feb 2011 12:41:06 -0500 Message-ID: <4D5ABAB2.2000405@redhat.com> Date: Tue, 15 Feb 2011 17:41:00 -0000 From: Richard Henderson User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7 MIME-Version: 1.0 To: =?UTF-8?B?UGV0ciBIbHV6w61u?= CC: Anitha Boyapati , gdb@sourceware.org, binutils@sourceware.org Subject: Re: Testing Call frame information in .debug_frame section References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2011-02/txt/msg00172.txt.bz2 On 02/13/2011 07:10 AM, Petr Hluzín wrote: > http://xfree86.cygwin.ru/ml/binutils/2010-08/msg00109.html I'll agree that a better error message would be helpful. To answer a question within that message: > By the way: Why AVR target does not understand CFI? What needs to be > done in binutils? And in GDB? TARGET_USE_CFIPOP DWARF2_DEFAULT_RETURN_COLUMN DWARF2_CIE_DATA_ALIGNMENT DWARF2_LINE_MIN_INSN_LENGTH are the macros that need to be defined, tc_cfi_frame_initial_instructions may be required depending on what the state of the unwind info incoming to a function. Have a look at tc-i386.c, tc_x86_frame_initial_instructions for a typical stack-based call mechanism. For the nearly related task of dwarf2 line numbers, you need a call to dwarf2_emit_insn emitted immediately before each insn is added to the frags. Again, see tc-i386.c for ideas. r~