From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16162 invoked by alias); 9 Jan 2003 03:12:10 -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 16151 invoked from network); 9 Jan 2003 03:12:08 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 209.249.29.67 with SMTP; 9 Jan 2003 03:12:08 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18WUza-00014v-00; Wed, 08 Jan 2003 23:12:34 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18WT7B-0002fG-00; Wed, 08 Jan 2003 22:12:17 -0500 Date: Thu, 09 Jan 2003 03:12:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: `chain-frame' Message-ID: <20030109031217.GA10222@nevyn.them.org> Mail-Followup-To: Andrew Cagney , gdb@sources.redhat.com References: <3E1CD9F5.4090607@redhat.com> <20030109023850.GA9277@nevyn.them.org> <3E1CE724.2090401@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E1CE724.2090401@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-01/txt/msg00110.txt.bz2 On Wed, Jan 08, 2003 at 10:06:12PM -0500, Andrew Cagney wrote: > >I'm trying, but I still don't quite see how you're laying this out. > >All help welcomed! Maybe I should look over your WIP again; has it > >changed since you last posted it? > > It's changed. I'm going to cut a branch. > > >regcache-frame (regs-frame?): > >>A frame that maps directly onto the register cache. > > > > > >Doesn't unwind, since we're at the top. > > Nope! At the bottom, and it does unwind. > > This unwinds to the ``inner most frame''. Instead of calling > create_new_frame(), get_current_frame() creates this frame and then > unwinds it. Oh, er. Right, I should have understood that by now. Thank you. > Another name for this one is: > > sentinal-frame > > since it acts as the sentinal one beyond the inner most frame. Great. (Sentinel btw). > >fake-frame (?): > >>Recently discussed, would also use dwarf2cfi but with fake debug > >>information. > > > > > >Unwinds using the CFI reader and fake DWARF-2 CFI information. Someday > >maybe have a more generalized "unwind language"; that's my hope, > >anyway. So we don't have to encode and decode the CFI gunk. > > Yes, and Yes. The later can just plug in. > > >And the other group of frames just use the current frame chain code, > >and poke at the stack to find the saved registers; maybe > >"stack-chain-frame"? > > Oops, yes. Just: > > chain-frame: > > though I think. This'll require playing around with my vocabulary a little to get used to it, but I can buy it. The general action is "unwinding"; looking for the "chain" is one mechanism. I like it. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer