From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5916 invoked by alias); 16 Mar 2003 22:04:38 -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 5878 invoked from network); 16 Mar 2003 22:04:38 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 16 Mar 2003 22:04:38 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D200C2B11 for ; Sun, 16 Mar 2003 17:04:36 -0500 (EST) Message-ID: <3E74F4F4.50003@redhat.com> Date: Sun, 16 Mar 2003 22:04: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: gdb@sources.redhat.com Subject: frame->unwind->this_base() Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00238.txt.bz2 At present there is a per-frame ID method since different frames determine their ID using different techniques. The ID (which identifies a given frame instance) includes a base and pc/func value. GDB's frame code also makes available the get_frame_base() method. While the default implementation returns get_frame_id().base, I think there is going to need to be a per-frame frame->unwind->this_base method. For dwarf2 frames, it would return, DW_AT_frame_base. For prologue frames, it would return an attempt at an equivalent value. Hopefully it wouldn't be called for other frame types :-). It might even be reasonable for a prologue based unwinder to error out when asked for the frame's base before the stack frame has been created. Thoughts? I should note that dwarf2expr.c contains code that tries to locally/directly evaluate the frame base. I think that should instead do a get_frame_base() call. Andrew