From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20330 invoked by alias); 9 Sep 2002 19:14:25 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 20323 invoked from network); 9 Sep 2002 19:14:21 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 9 Sep 2002 19:14:21 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 068713F26; Mon, 9 Sep 2002 15:14:19 -0400 (EDT) Message-ID: <3D7CF30A.9040902@ges.redhat.com> Date: Mon, 09 Sep 2002 12:14:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Kettenis , Joel Brobecker , Michael Snyder Cc: gdb-patches@sources.redhat.com Subject: Re: native or target? References: <20020905232440.GV1169@gnat.com> <20020905232935.GF1194@gnat.com> <3D77F391.85509705@redhat.com> <20020906010247.GX1169@gnat.com> <863csmq4rp.fsf@elgar.kettenis.dyndns.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-09/txt/msg00125.txt.bz2 > >> BTW: Is it a requirement for a new port to be buildable as a target >> only, or can we provide a native-only port as a first step, and then >> eventually improve it to support "--host=--target=interix"? This is >> out-of-the-box thinking, I don't see how this would help the problem we >> have been discussing, but I think this is an interesting piece of >> information to know. > > > I'm inclined to say yes. If I can configure GDB with > --target=i386-interix on my i386-freebsd system, I can test the > target-dependent code, and you run a smaller risk of me accidentally > breaking your port when making changes to the common i386 code. Two conflicting answers, hmm :-) It's all smoke and mirrors anyway. What gets built with the cross debugger is determined by what is listed in config/i386/interix.mt. If a file isn't in that list then it won't get built so no one will see the problems it contains ;-) As Mark points out, it is very much to your advantage to have all code working as a cross target. Anyway, I think this thread has identified the need for a i386-interix-tdep.c file. If you haven't already, I think a good easy (????) step would be to create an (almost) empty i386-interix-tdep.c that just contains the interix ``sniffer''. Since you'll be needing to override architecture methods, you'll definitly need this bit of infrastructure working. Andrew