From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31132 invoked by alias); 4 Dec 2003 23:05:44 -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 31114 invoked from network); 4 Dec 2003 23:05:43 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 4 Dec 2003 23:05:43 -0000 Received: from drow by nevyn.them.org with local (Exim 4.24 #1 (Debian)) id 1AS2XT-0002JZ-Ac; Thu, 04 Dec 2003 18:05:39 -0500 Date: Thu, 04 Dec 2003 23:05:00 -0000 From: Daniel Jacobowitz To: Nitin Gupta Cc: Andrew Cagney , Ian Lance Taylor , gdb@sources.redhat.com Subject: Re: GDB for Multiprocessor Architecture Message-ID: <20031204230538.GA8795@nevyn.them.org> Mail-Followup-To: Nitin Gupta , Andrew Cagney , Ian Lance Taylor , gdb@sources.redhat.com References: <36993D449C7FA647BF43568E0793AB3E32A603@nevis_pune_xchg.pune.nevisnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <36993D449C7FA647BF43568E0793AB3E32A603@nevis_pune_xchg.pune.nevisnetworks.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-12/txt/msg00095.txt.bz2 On Fri, Dec 05, 2003 at 02:35:47AM +0530, Nitin Gupta wrote: > > > CPU's can be modeled using GDB's thread framework. However, > > at present > > the model doesn't extend as far as modeling separate memory > > regions for > > each CPU (something that needs to be fixed). > > > I need this feature for my model and I am ready to enhance this feature > in GDB. > However, I have some queries. GDB remote protocol does not have a field > that can tell me about the processor (thread) id. This means that can I > on-the-fly switch from one thread to another? I feel this has to be > incorporated in the protocol. Hence it will be comething like every > message actually coming with the processor id attached with it. > I plan to extend the GDB remote protocol and make changes in remote.c > file. Roghly how big this enhancemet will be? > Has anybody done work on this earlier? Where can I find some more > documents on the remote protocol. The code obviously is the best doc. Take a look at the existing thread specification packets in the remote protocol. It is documented in the GDB manual, available online or in Texinfo format in the source tree. You want the Appendix named Remote Serial Protocol. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer