From: Markus Deuling <deuling@de.ibm.com>
To: Nitin Gupta <ngupta@mvista.com>
Cc: gdb@sourceware.org
Subject: Re: Debugging support multi-core/smp systems
Date: Thu, 20 Sep 2007 16:54:00 -0000 [thread overview]
Message-ID: <46F2A390.9040700@de.ibm.com> (raw)
In-Reply-To: <46F1AA15.2060804@mvista.com>
Hi Nitin,
Nitin Gupta schrieb:
> What debug capabilities does latest gdb have for multi-core/SMP systems?
> Please let me know about both homogeneous and heterogeneous systems.
as Cell B./E. (e.g. Playstation 3) is a heterogeneous multi-core processor you may want to take
a look at the 'combined debugger' (ppu-gdb) found here: http://www.bsc.es/projects/deepcomputing/linuxoncell/
'spu-gdb' is the spu-only port of GDB to debug SPU applications. 'ppu-gdb' is capable of debugging applications
consisting of both PPU (PowerPC 970) and SPU parts (e.g. cross-architecture backtraces).
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
prev parent reply other threads:[~2007-09-20 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 5:58 Nitin Gupta
2007-09-20 15:30 ` Ramana Radhakrishnan
2007-09-20 16:54 ` Markus Deuling [this message]
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=46F2A390.9040700@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=gdb@sourceware.org \
--cc=ngupta@mvista.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