Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Bridge Wu <mingqiao.wu@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb for multicore processors?
Date: Fri, 29 Sep 2006 18:10:00 -0000	[thread overview]
Message-ID: <1159553397.9768.259.camel@localhost.localdomain> (raw)
In-Reply-To: <246188420609282029u672a8ff7nc836c2cda35cf95@mail.gmail.com>

On Fri, 2006-09-29 at 11:29 +0800, Bridge Wu wrote:
> Hello,
> 
> I want to know whether gdb support multicore debugging now. I searched
> below from this mailing list, but didn't know the current status. Is
> there any plan or roadmap to support multicore debugging?

The most interesting "thread" of conversation (pun intended) 
that I've taken part in has been with the idea that, if they 
are symmetric multi-processors and if they are running the same
code, we could somehow hoax them into the thread model.  Treat
each core as a thread.

This could for instance be done with cooperation from the 
target side.  If gdb were talking to a remote stub or 
gdbserver, then the remote side could simply report each
core using a different "thread id", and to gdb it would be
transparent.



  reply	other threads:[~2006-09-29 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29  3:30 Bridge Wu
2006-09-29 18:10 ` Michael Snyder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-08  5:47 gdb for multicore processors ? Kim Lux
2005-12-08  5:49 ` Kim Lux
2005-12-08 13:56   ` Daniel Jacobowitz

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=1159553397.9768.259.camel@localhost.localdomain \
    --to=michael.snyder@palmsource.com \
    --cc=gdb@sources.redhat.com \
    --cc=mingqiao.wu@gmail.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