From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10375 invoked by alias); 7 Apr 2002 01:23:51 -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 9082 invoked from network); 7 Apr 2002 01:23:44 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 7 Apr 2002 01:23:44 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 6F32A3CB7; Sat, 6 Apr 2002 20:23:26 -0500 (EST) Message-ID: <3CAF9F8E.6030607@cygnus.com> Date: Sat, 06 Apr 2002 17:23:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.9) Gecko/20020328 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Berlin Cc: gdb-patches@sources.redhat.com Subject: Re: [WIP]: LOC_COMPUTED and LOC_COMPUTED_ARG References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg00242.txt.bz2 > and >> > >> > - the frame base address (for DW_OP_fbreg) >> > >> > >> > Not possible. >> > the frame base can be a location list. >> > That's why it pulls it out of the frame function on the fly. > >> >> Something I've never understood. Shouldn't frame_base be stored in >> frame->base as part of the initial frame creation. Hence avoiding this >> recursion? > > > Theoretically you could, but it's sort of pointless. > You still end up doing the same lookup. > It also hides the code, since the code to create frames is nowhere > near the dwarf2 reader. I'm still missing something. If dwarf2 info isn't used to compute frame->base (and frame->prev->pc) where are the values comming from? Andrew