From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22186 invoked by alias); 30 Jan 2002 05:20:31 -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 22045 invoked from network); 30 Jan 2002 05:20:30 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.26.18) by sources.redhat.com with SMTP; 30 Jan 2002 05:20:30 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id 960203DD0; Wed, 30 Jan 2002 00:20:24 -0500 (EST) Message-ID: <3C578298.3000108@cygnus.com> Date: Tue, 29 Jan 2002 21:20:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Dan Kegel Cc: Daniel Jacobowitz , gdb@sources.redhat.com Subject: Re: How does one cross-compile gdbserver? References: <3C574C25.8A2F007@kegel.com> <20020129205052.B19879@nevyn.them.org> <3C575A1C.5020700@cygnus.com> <3C576C11.FFE78FE1@kegel.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00348.txt.bz2 >> > I don't give it good odds of compiling. I've tried several times to >> > clean that up and gotten stymied in various people's objections to my >> > methods (sorry Andrew). I'll be taking another stab at it this week I >> > think. > >> >> :-) >> >> I've been thinking about making it obsolete. Not that I want to lose >> it. Rather that it clears the slate and removes any obligation to keep >> other targets working. > > > If you make gdbserver obsolete, what would you replace it with? gdbserver > There's no question that some sort of remote debugging probe > is a must for embedded development (personally, I use printf, > but 90% of developers would much prefer to use a debugger). The current GDBSERVER is rapidly decaying. This is occuring chiefly because core gdb is being multi-arched (multi-arch is about a GDB with support for multiple architectures / OSs / shlibs). I don't think Daniel's core problem is being stymied by peoples objections but rather the obligation to keep (or at least try to keep) existing gdbservers working. If GDBSERVER is declared obsolete or (a better way of putting it) completly broken then the obligation to keep things working really isn't relevant. enjoy, Andrew PS: Daniel, did you ever do that signals.h header file?