From: "Nitin Gupta" <nitin.gupta@nevisnetworks.com>
To: "Andrew Cagney" <cagney@gnu.org>
Cc: "Daniel Jacobowitz" <drow@mvista.com>,
"Ian Lance Taylor" <ian@wasabisystems.com>,
<gdb@sources.redhat.com>
Subject: RE: GDB for Multiprocessor Architecture
Date: Thu, 04 Dec 2003 21:05:00 -0000 [thread overview]
Message-ID: <36993D449C7FA647BF43568E0793AB3E32A603@nevis_pune_xchg.pune.nevisnetworks.com> (raw)
> 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.
Nitin Gupta
next reply other threads:[~2003-12-04 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 21:05 Nitin Gupta [this message]
2003-12-04 23:05 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-12-05 11:01 Nitin Gupta
2003-12-03 14:07 Nitin Gupta
2003-12-03 18:28 ` Andrew Cagney
2003-12-05 7:28 ` Amit S. Kale
2003-12-14 3:32 ` Mark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36993D449C7FA647BF43568E0793AB3E32A603@nevis_pune_xchg.pune.nevisnetworks.com \
--to=nitin.gupta@nevisnetworks.com \
--cc=cagney@gnu.org \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=ian@wasabisystems.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox