From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31898 invoked by alias); 9 Jan 2003 02:11:25 -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 31635 invoked from network); 9 Jan 2003 02:10:06 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by 209.249.29.67 with SMTP; 9 Jan 2003 02:10:06 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 9606F3EC2 for ; Wed, 8 Jan 2003 21:09:57 -0500 (EST) Message-ID: <3E1CD9F5.4090607@redhat.com> Date: Thu, 09 Jan 2003 02:11:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.1) Gecko/20021211 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: `chain-frame' Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg00106.txt.bz2 I've been looking for a better name for the mechanism the targets currently use when unwinding a frame. I've been using saved-regs frame, but that is pretty pervasive - all frames contain saved regs. I'm thinking of instead calling it a `chain-frame' since the existing mechanism relies not just on the frame->saved_regs[] array but also the FRAME_CHAIN() method. This means that there are so far potentially: dummy-frame: Created when doing an inferior function call. regcache-frame (regs-frame?): A frame that maps directly onto the register cache. cfi-frame: Implemented using dwarf2cfi (this is the holy grail) sigtramp-frame: Corresponds to a signal trampoline. fake-frame (?): Recently discussed, would also use dwarf2cfi but with fake debug information. Andrew