From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10616 invoked by alias); 9 May 2003 21:58:32 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 10607 invoked from network); 9 May 2003 21:58:32 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.131) by sources.redhat.com with SMTP; 9 May 2003 21:58:32 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 780C42B2F; Fri, 9 May 2003 17:58:26 -0400 (EDT) Message-ID: <3EBC2482.2010203@redhat.com> Date: Fri, 09 May 2003 21:58:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Mark Kettenis , gdb@sources.redhat.com Subject: Re: [RFC] DWARF CFI: what to do with .eh_frame sections? References: <200305092014.h49KEYPd020771@elgar.kettenis.dyndns.org> <20030509202040.GA27956@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg00164.txt.bz2 > On Fri, May 09, 2003 at 10:14:34PM +0200, Mark Kettenis wrote: > >> It's clear that we want to support unwinding using info in .eh_frame >> sections in addition to .debug_frame sections. I'm inclined to make >> to make dwarf-frame.c provide two frame unwinders: one that uses >> .debug_frame info, and one that uses .eh_frame info. That way it will >> be possible to let the target determine if .dwarf_frame will be >> preferred over .eh_frame or not. >> >> Thoughts? > > > That seems reasonable. I'd probably create a single function to > register both unwinders, and call it from each target, though; > since there's no reason I can think of to prefer one over the other > modula unknown GDB bugs. Think of it as a two tiered effect, you know with ... (sorry). If I understand the cfi stuff correctly, it can be broken down into: - the cfi engine - the cfi byte stream source (kind of like dwarf2expr) The latter can be debug info, .eh_frame, or even (as long a go proposed) hand written code. Andrew