From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15497 invoked by alias); 30 Dec 2002 23:58:32 -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 15488 invoked from network); 30 Dec 2002 23:58:31 -0000 Received: from unknown (HELO mail.s.netic.de) (212.9.160.11) by 209.249.29.67 with SMTP; 30 Dec 2002 23:58:31 -0000 Received: from isdn049.s.netic.de ([212.9.162.49] helo=schleim.qwe.de) by mail.s.netic.de with esmtp (Exim 4.10) id 18T9jr-0005uy-00; Tue, 31 Dec 2002 00:54:31 +0100 Received: from schleim (localhost [127.0.0.1]) by schleim.qwe.de (Postfix) with ESMTP id 7070BB60; Tue, 31 Dec 2002 00:31:17 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Torsten Mohr To: Daniel Jacobowitz Subject: Re: patching gdb, adding files for certain combinations of host/target Date: Mon, 30 Dec 2002 15:58:00 -0000 User-Agent: KMail/1.4.3 Cc: gdb References: <200212310000.50719.tmohr@s.netic.de> <20021230233228.GA17265@nevyn.them.org> In-Reply-To: <20021230233228.GA17265@nevyn.them.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200212310031.16324.tmohr@s.netic.de> X-SW-Source: 2002-12/txt/msg00341.txt.bz2 Hi, > Right now there's no obvious way, but I'm sure it could be managed if > it was needed. Let me ask a different question: why do you want to do > this? A design goal for GDB is that it shouldn't matter what your host > is. I wrote a library available at: http://www.s.netic.de/tmohr/pppcb-0.2.0.tar.gz (There's a newer, better version available, but not yet on that web page). It does several things with the parallel port, for example debugging an ARM via a software JTAG over the parallel port. This only makes sense for the target ARM. The library also has some abstraction for accessing the parallel port, but i'd like to only compile everything at the moment for host linux and target ARM. Only for Linux i know how to access the parallel port in user space. Also, i took a look at a patch mpcbdm-1.2.3.tar.gz available at SourceForge (a patch to debug a PowerPC via the parallel port). This patch wasn't compiled because (i think so) i chose target "powerpc-unknown-elf" and the author seems to use the target "powerpc-linux". So he has put the target object file dependencies in a file gdb/config/powerpc/linux.mt. I tried to change that patch in a way that makes it compile for target powerpc but failed. I'm far from being an experienced gdb programmer, though i read this list for quite a while now. As several micros have debug interfaces like BDM or JTAG, i think it would be useful to add an abstraction for the parallel port (host dependent) and based on that some more debug interfaces. This could increase the usage of gdb for cross development a lot. I'm glad for any hints you could give. Best regards, Torsten.