From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9514 invoked by alias); 25 Jun 2003 18:28:55 -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 27395 invoked from network); 25 Jun 2003 17:03:03 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 25 Jun 2003 17:03:03 -0000 Received: from dsl093-172-017.pit1.dsl.speakeasy.net ([66.93.172.17] helo=nevyn.them.org ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 19VDgW-0000hn-00; Wed, 25 Jun 2003 12:03:52 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19VDfZ-00067I-00; Wed, 25 Jun 2003 13:02:53 -0400 Date: Wed, 25 Jun 2003 18:28:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: Enable frame-base before frame-unwind? Message-ID: <20030625170253.GA23496@nevyn.them.org> Mail-Followup-To: Andrew Cagney , gdb@sources.redhat.com References: <3EF9C2F1.7040904@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EF9C2F1.7040904@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-06/txt/msg00477.txt.bz2 On Wed, Jun 25, 2003 at 11:42:41AM -0400, Andrew Cagney wrote: > Here's a new theory on how to migrate to the unwind code: > > Enable frame-base before frame-unwind. > > Why? The frame-unwind code can't be enabled until frame-base is working > anyway. Since frame-base is an almost direct replacement for > FRAME_LOCALS_ADDRESS and FRAME_ARGS_ADDRESS, and the return values for > the old/new methods are the same, I think getting frame-base working is > going to be much easier than getting frame-unwind working. Since > frame-base and frame-unwind share the prologue analysis code, debugging > it with the less harmful frame-base should make life easier. > > Any one want to prove the theory? ... sure. I think you've answered this once already, but is there a list of routines that have needed to change, so far? Or do I need to put one together as I go along? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer