From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22531 invoked by alias); 24 Nov 2008 22:03:21 -0000 Received: (qmail 21996 invoked by uid 22791); 24 Nov 2008 22:03:19 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 24 Nov 2008 22:02:15 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id AD4CF10D50; Mon, 24 Nov 2008 22:02:04 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 9DFE210AD3; Mon, 24 Nov 2008 22:02:04 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1L4jVM-0002Kq-2j; Mon, 24 Nov 2008 17:02:04 -0500 Date: Mon, 24 Nov 2008 22:03:00 -0000 From: Daniel Jacobowitz To: Duane Ellis Cc: gdb@sourceware.org Subject: Re: GDB for multiple targets Message-ID: <20081124220204.GA8666@caradoc.them.org> Mail-Followup-To: Duane Ellis , gdb@sourceware.org References: <492AD78E.4040905@duaneellis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <492AD78E.4040905@duaneellis.com> User-Agent: Mutt/1.5.17 (2008-05-11) 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: 2008-11/txt/msg00146.txt.bz2 On Mon, Nov 24, 2008 at 11:34:22AM -0500, Duane Ellis wrote: > Are you describing additional items in "target.xml" that GDB requests > from the remote? Right. > If so - what about other items, such as target endian, cputype (or in arm > terms, "arch") and perhaps a flag that indicates the target is "bare > metal" and not an operating system based target? We can add pretty much anything there that is useful. Architecture is already supported (), or is that not sufficient? The OSABI setting that Ulrich is referring to covers the bare metal / OS distinction, too. Endianness is not currently present but would be an easy addition. I haven't bothered, because in most cases you have an executable file; that doesn't tell you the CPU arch, but it does tell you the endianness. -- Daniel Jacobowitz CodeSourcery