From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25353 invoked by alias); 23 Jan 2007 22:57:18 -0000 Received: (qmail 25343 invoked by uid 22791); 23 Jan 2007 22:57:17 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Tue, 23 Jan 2007 22:57:12 +0000 Received: from drow by nevyn.them.org with local (Exim 4.63) (envelope-from ) id 1H9UZh-000114-IX; Tue, 23 Jan 2007 17:57:09 -0500 Date: Tue, 23 Jan 2007 22:57:00 -0000 From: Daniel Jacobowitz To: "Dominique Toupin (QA/EMC)" Cc: gdb@sourceware.org Subject: Re: gdb remote stub for proprietary operating system? Message-ID: <20070123225709.GA3793@nevyn.them.org> Mail-Followup-To: "Dominique Toupin (QA/EMC)" , gdb@sourceware.org References: <20070123214603.GA495@nevyn.them.org> <67048CBE51B1644D89DDD3B7C9F2D19E02EDE60E@ecamlmw720.eamcs.ericsson.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <67048CBE51B1644D89DDD3B7C9F2D19E02EDE60E@ecamlmw720.eamcs.ericsson.se> User-Agent: Mutt/1.5.13 (2006-08-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: 2007-01/txt/msg00302.txt.bz2 On Tue, Jan 23, 2007 at 05:45:36PM -0500, Dominique Toupin (QA/EMC) wrote: > Hi, > > I have this info > http://sourceware.org/gdb/current/onlinedocs/gdb_18.html#SEC165, when > they say we can ignore the details I was hopping we could ignore the > communication protocol. > Do we have documentation other than sparc-stub.c? That is not a good place to look for an OS stub. Look at the appendix which documents the communication protocol - I think it's Appendix D. You will almost certainly need to write your own implementation of that, connected to your proprietary debug interface. And it will give you a good idea of what is expected of a remote stub. If you have threads, you'll probably want vCont. You'll need at least g/G and m/M (or X). If you have code in non-writeable or shared memory, you'll need the z/Z packets. And so forth. > If you have to choose between 3 months, 6 months, 1 year, 2 years, what > would be the guess for how long it would take 1 person to implement the > remote stub to support all the GDB/MI commands? It depends on the questions I asked, and the experience of the people working on the project. It is probably more like a six month project than like a one year project. Of course, if you need a better estimate than that, there are a number of companies who can do this sort of project :-) -- Daniel Jacobowitz CodeSourcery