This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: GDB for Multiprocessor Architecture
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Nitin Gupta <nitin dot gupta at nevisnetworks dot com>
- Cc: Andrew Cagney <cagney at gnu dot org>,Ian Lance Taylor <ian at wasabisystems dot com>, gdb at sources dot redhat dot com
- Date: Thu, 4 Dec 2003 18:05:39 -0500
- Subject: Re: GDB for Multiprocessor Architecture
- References: <36993D449C7FA647BF43568E0793AB3E32A603@nevis_pune_xchg.pune.nevisnetworks.com>
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