From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21456 invoked by alias); 30 Mar 2007 21:02:49 -0000 Received: (qmail 21426 invoked by uid 22791); 30 Mar 2007 21:02:47 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 30 Mar 2007 22:02:45 +0100 Received: (qmail 7590 invoked from network); 30 Mar 2007 21:02:43 -0000 Received: from unknown (HELO localhost) (jimb@127.0.0.2) by mail.codesourcery.com with ESMTPA; 30 Mar 2007 21:02:43 -0000 To: Michael Eager Cc: gdb@sources.redhat.com Subject: Re: GDB Documentation and Request for Help References: <460D46B7.10902@eagercon.com> <460D565F.3070307@eagercon.com> <20070330184051.GA26862@caradoc.them.org> From: Jim Blandy Date: Fri, 30 Mar 2007 21:02:00 -0000 In-Reply-To: <20070330184051.GA26862@caradoc.them.org> (Daniel Jacobowitz's message of "Fri, 30 Mar 2007 14:40:51 -0400") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-03/txt/msg00344.txt.bz2 Daniel Jacobowitz writes: > On Fri, Mar 30, 2007 at 11:26:39AM -0700, Michael Eager wrote: >> Jim Blandy wrote: > >> >If you post here, I think people would be happy to explain what's >> >current and what isn't. I'll watch for your messages. > >> Thanks. I think that my questions are not very specific and >> it would be better to go through the Target Arch chapter >> and mark it up. > >> But here goes: what did FRAME_INIT_SAVED get replaced by? > > It got replaced by an entirely demand driven system. There's only two > entry points: this_id and prev_register. Every registered unwinder > provides both. Michael, your question suggests that you're looking at some code in your old port, and trying to figure out where it goes in your new port. I would find that a very hard question to answer if I were in your shoes. Instead, start by reading frame-unwind.h and having your foo_gdbarch_init function call frame_unwind_append_sniffer with a structure containing appropriate functions, written from scratch. In other words, you may be able to use the old port to understand how your target works, but you'll need to decide afresh how to express that understanding in the new arch description framework. (Having worked on both, I think the new frame system is *much* nicer to work with, and more reliable. So your efforts won't be wasted.)