From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4359 invoked by alias); 29 May 2003 09:49:58 -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 4279 invoked from network); 29 May 2003 09:49:55 -0000 Received: from unknown (HELO cam-admin0.cambridge.arm.com) (193.131.176.54) by sources.redhat.com with SMTP; 29 May 2003 09:49:55 -0000 Received: from pc960.cambridge.arm.com (pc960.cambridge.arm.com [10.1.205.4]) by cam-admin0.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id KAA15914; Thu, 29 May 2003 10:49:54 +0100 (BST) Received: from pc960.cambridge.arm.com (rearnsha@localhost) by pc960.cambridge.arm.com (8.11.6/8.9.3) with ESMTP id h4T9nso00798; Thu, 29 May 2003 10:49:54 +0100 Message-Id: <200305290949.h4T9nso00798@pc960.cambridge.arm.com> X-Authentication-Warning: pc960.cambridge.arm.com: rearnsha owned process doing -bs To: "Svein E. Seldal" cc: gdb@sources.redhat.com, Richard.Earnshaw@arm.com Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. Subject: Re: Porting advice or documentation request In-reply-to: Your message of "Thu, 29 May 2003 00:55:20 +0200." <3ED53E58.5070502@solidas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 May 2003 09:49:00 -0000 From: Richard Earnshaw X-SW-Source: 2003-05/txt/msg00383.txt.bz2 > Hi all, > > I'm working on this new gdb port, and more than often I'm stuck. I have > been told that the d10v port is the most authorative template for how > new targets should be written. Unfortunately it is impossible to learn > anything about the d10v's hardware architecture on the net, so I find it > a bit difficult to template from. I can sympathise. I've tried on a couple of occasions to update the ARM target to use the new interfaces and I've repeatedly run into situations where the GDB's abstraction model is just not obvious from staring at the code. Andrew, I think we really need a 10,000 ft view document on gdb's internal architecture to complement the list of macros that a target can define... R.