From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12860 invoked by alias); 1 Feb 2002 03:29:28 -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 12826 invoked from network); 1 Feb 2002 03:29:23 -0000 Received: from unknown (HELO localhost.cygnus.com) (216.138.202.10) by sources.redhat.com with SMTP; 1 Feb 2002 03:29:23 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id 747013DF3; Thu, 31 Jan 2002 22:29:15 -0500 (EST) Message-ID: <3C5A0B8B.7080504@cygnus.com> Date: Thu, 31 Jan 2002 19:29: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: Quality Quorum , Daniel Jacobowitz Cc: Michael Snyder , "Sarnath K - CTD, Chennai." , gdb@sources.redhat.com Subject: Re: Thread Support for remote debugging References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00388.txt.bz2 >> No, he means "knowing whether GDB and GDB Server support doing remote >> debugging at all", as far as I can tell. >> >> We've covered this ground a couple times lately :) Someone promised to >> contribute thread support and dropped off the face of the earth. It's >> on my TODO list, but I don't anticipate getting to it any time soon. >> Etc. (I recall the discussion, from memory one of the problems was the paper trail). Daniel, you might consider doing what I do with my TODO list - just shove it all into GDB's bug database as change-requests :-) > If you are talking about me, I had it done more than one year ago: > http://world.std.com/~qqi, see section about gdb. Daniel isn't. > The problem is that (1) redhat never said 'yes we want it' so it is > sitll based on 4.18, (2) there are a few issues which could be > resolved one way or anotehr an readhat never said 'we want it this way'. (GDB is owned by the FSF (not Red Hat) and it is assumed that GDB developers put the FSF's interests before their own.) GDB currently comes with: gdb/*-stub.c: These are primative stubs that can be run on embedded boards. They appear to be public domain. gdb/gdbserver: This lets you debug a native UNIX program on a remote machine. It is GPLed. It is owned by the FSF. Within the embedded community I suspect it is a hot product since it lets the developer debug a UNIX application running on the embedded machine remotely. My understanding of rproxy was that it could be linked with third party libraries and provide a remote protocol interface to JTAG devices and the like. I wasn't aware that it could be used to do remote debugging of native applications. As for making rproxy part of GDB, I'm certainly interested (I didn't know you were looking to do this). Since gdbserver is both owned by the FSF and is GPL, I would need to ensure that its replacement is no less ``free''. Would you be willing to contribute rproxy to the FSF? Andrew