From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22932 invoked by alias); 23 Apr 2002 23:09:49 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 22856 invoked from network); 23 Apr 2002 23:09:42 -0000 Received: from unknown (HELO cygnus.com) (205.180.83.203) by sources.redhat.com with SMTP; 23 Apr 2002 23:09:42 -0000 Received: from romulus.sfbay.redhat.com (romulus.sfbay.redhat.com [172.16.27.251]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id QAA08814; Tue, 23 Apr 2002 16:09:42 -0700 (PDT) Received: (from kev@localhost) by romulus.sfbay.redhat.com (8.11.6/8.11.6) id g3NN9eD10852; Tue, 23 Apr 2002 16:09:40 -0700 Date: Tue, 23 Apr 2002 16:09:00 -0000 From: Kevin Buettner Message-Id: <1020423230940.ZM10851@localhost.localdomain> In-Reply-To: "David S. Miller" "[RFA] Locate sparc64 arguments correctly" (Apr 20, 2:09am) References: <20020420.020906.44150275.davem@redhat.com> To: "David S. Miller" , gdb-patches@sources.redhat.com Subject: Re: [RFA] Locate sparc64 arguments correctly MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-04/txt/msg00886.txt.bz2 On Apr 20, 2:09am, David S. Miller wrote: > 1) Debugging information encodes LOC_ARG/LOC_REF_ARG offsets > with the Sparc64 stack bias included, we keep track of the > frame pointer with the stack bias removed on sparc64. > > sparc64_frame_args_address takes care of that. I agree that this is the problem, but, when you do this... > +/* Debugging information stores LOC_ARG/LOC_REF_ARG offsets with the > + sparc64 stack bias present, this undoes that so that users of > + FRAME_ARGS_ADDRESS use the right location. */ > + > +static CORE_ADDR > +sparc64_frame_args_address (struct frame_info *fi) > +{ > + return fi->frame - 2047; > +} ...does the output from ``info frame'' still look reasonable?