From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: denis.pilat@st.com (Denis PILAT),
gdb@sourceware.org,
dominique.toupin@ericsson.com ("Dominique Toupin
(QA/EMC)")
Subject: Re: Improving GDB for multicore and embedded system!
Date: Mon, 05 Mar 2007 16:51:00 -0000 [thread overview]
Message-ID: <200703051651.l25GpTtn010709@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070302135424.GA30113@caradoc.them.org> from "Daniel Jacobowitz" at Mar 02, 2007 08:54:24 AM
Daniel Jacobowitz wrote:
> On Fri, Mar 02, 2007 at 10:08:55AM +0100, Denis PILAT wrote:
> > Today multicore debugging means multiple instance of gdb running at the
> > same time. I don't know how possible it is to enhance gdb so that it can
> > handle multiple programs running on different architecture.
> > I guess Daniel should have a good vision on that.
>
> No one has ever convinced me that there's a good reason to do this,
> rather than wire up things like DSF to drive multiple GDB's, if the
> cores are not all running the same architecture and program image. If
> they are, we generally present them as threads, and that works very
> well.
>
> However, I have relatively little experience with non-symmetric
> multicore debugging - I have a board lab at home but it doesn't
> include any multicore targets, and we haven't done much with them at
> my job, either. I'm always interested in learning more about new
> debugging models, or having an opportunity to do work on them.
We have a version of GDB that supports multi-architecture debugging
(PowerPC + SPU) on Linux for the Cell BE. This is currently not
merged upstream (and the code isn't really in a mergeable state).
[ If you're interested, a GDB source RPM including those patches is
available at http://www.bsc.es/projects/deepcomputing/linuxoncell/ ]
However, we do intend to work on common GDB infrastructure with
the goal of having mainline GDB support multi-architure debugging.
The plan here basically is:
- Complete GDB's multi-arch transition (get rid of tm.h files)
--> This will allow multiple architectures to be compiled into
a single GDB executable
- Switch from the global current_gdbarch to per-frame gdbarch
--> This should allow use of multiple architectures
concurrently within a single inferior process
None of that is really news; GDB has been moving into that
direction for a long time. It does look like with a bit of
additional effort (which we'd be willing to help put in), it
should be possible to complete those transitions in the
not-too-distant future.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2007-03-05 16:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 16:39 Dominique Toupin (QA/EMC)
2007-03-01 17:00 ` Dominique Toupin (QA/EMC)
2007-03-01 17:08 ` Dominique Toupin (QA/EMC)
2007-03-02 9:09 ` Denis PILAT
2007-03-02 10:04 ` Dominique Toupin (QA/EMC)
2007-03-02 13:54 ` Daniel Jacobowitz
2007-03-02 14:21 ` Fabian Cenedese
2007-03-02 14:31 ` Daniel Jacobowitz
2007-03-02 15:04 ` Ramana Radhakrishnan
2007-03-02 15:22 ` Paul Koning
2007-03-05 16:51 ` Ulrich Weigand [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=200703051651.l25GpTtn010709@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=denis.pilat@st.com \
--cc=dominique.toupin@ericsson.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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