From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13484 invoked by alias); 18 Mar 2003 20:22:23 -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 13450 invoked from network); 18 Mar 2003 20:22:22 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 18 Mar 2003 20:22:22 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id C25C32B11; Tue, 18 Mar 2003 15:22:17 -0500 (EST) Message-ID: <3E777FF9.10005@redhat.com> Date: Tue, 18 Mar 2003 20:22: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: gdb@sources.redhat.com Subject: Re: frame->unwind->this_base() References: <20030317171142.GA15367@nevyn.them.org> <3E7611EC.3020304@redhat.com> <20030317193537.GA11288@nevyn.them.org> <3E7670F6.9060906@redhat.com> <20030318051348.GA19741@nevyn.them.org> <3E773325.8090001@redhat.com> <20030318155007.GA26362@nevyn.them.org> <3E775106.8030609@redhat.com> <20030318171124.GA27974@nevyn.them.org> <3E77574F.2010407@redhat.com> <20030318173814.GA28471@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00284.txt.bz2 > On Tue, Mar 18, 2003 at 12:28:47PM -0500, Andrew Cagney wrote: > >> >That would be a very bad assumption. They are pratically guarenteed to > >> >>be different. > >> > >> > >> >Then what do you mean by a "dwarf2 frame"? I'd assume you meant the >> >CFA, but it sounds like you mean a frame for which we have dwarf2 >> >.debug_info. > >> >> A frame with debug info provided by dwarf2. CFI gives the register >> info, location expressions give the variable info, ... >> >> What started out as a simple cfi-frame looks like it might need to >> evolve into dwarf2-frame ... > > > DWARF-2 debug info does not corelate with CFI info. For instance, GCC > will generate DWARF-2 CFI with stabs debug info. It will also generate > CFI with no debug info at all, or DWARF-2 info without any CFI (if > requested). True dwarf2 debug info or that .eh_frame stuff (i'm curious)? For stabs to work, it needs FRAME_LOCALS_ADDRESS(); and FRAME_LOCALS_ADDRESS() relies on the prologue analyzer (since frame ID won't correspond to `frame-base') for the computation of the correct value; and that means unwinding the same frame two ways. Outch. Andrew