From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19880 invoked by alias); 18 Sep 2009 14:39:17 -0000 Received: (qmail 19869 invoked by uid 22791); 18 Sep 2009 14:39:16 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 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; Fri, 18 Sep 2009 14:39:12 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 6F57810C63; Fri, 18 Sep 2009 14:39:10 +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 3991510927; Fri, 18 Sep 2009 14:39:10 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1Moec9-0002ps-EN; Fri, 18 Sep 2009 10:39:09 -0400 Date: Fri, 18 Sep 2009 14:39:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis Cc: uweigand@de.ibm.com, brobecker@adacore.com, teawater@gmail.com, gdb-patches@sourceware.org, msnyder@vmware.com Subject: Re: [RFA] Check solib bfd arch Message-ID: <20090918143909.GA10099@caradoc.them.org> Mail-Followup-To: Mark Kettenis , uweigand@de.ibm.com, brobecker@adacore.com, teawater@gmail.com, gdb-patches@sourceware.org, msnyder@vmware.com References: <200909181250.n8ICoMmD010948@d12av02.megacenter.de.ibm.com> <200909181407.n8IE7ktV013370@brahms.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909181407.n8IE7ktV013370@brahms.sibelius.xs4all.nl> User-Agent: Mutt/1.5.20 (2009-06-14) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00593.txt.bz2 On Fri, Sep 18, 2009 at 04:07:46PM +0200, Mark Kettenis wrote: > I suppose we needsto add the necessary magic to sparc-sol-nat.c to set > the proper architecture. I'll need to figure out how to extract that > information from the system. Is it possible to create a target > description that just contains the architecture and not all the > register stuff? Yes, this is easy. If there aren't any registers, the register bits will be disabled. The XML version would be something like: sparc:sparcv9 Solaris The C version could be generated from that, or if you want to do it dynamically: struct target_desc *result = allocate_target_description (); set_tdesc_architecture (result, my_bfd_arch_info_ptr); After that, mips_linux_read_description is a simple example of how to supply the description. I suspect the check is going to be problematic whether we do this or not, though. -- Daniel Jacobowitz CodeSourcery