From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: nathan@codesourcery.com (Nathan Sidwell)
Cc: gdb@sourceware.org, jimb@codesourcery.com (Jim Blandy)
Subject: Re: Non-stop multi-threaded debugging
Date: Tue, 27 Nov 2007 16:42:00 -0000 [thread overview]
Message-ID: <200711271642.lARGglTe031746@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <4743178A.3050501@codesourcery.com> from "Nathan Sidwell" at Nov 20, 2007 05:21:14 PM
Nathan Sidwell wrote:
> A client of CodeSourcery's has contracted with us to implement a
> number of new features in GDB, some of which have been on the
> frequently requested list for quite some time:
Thanks, these are indeed very interesting and useful features.
> - We're to implement a limited form of multi-process debugging.
>
> Full multi-process debugging would entail changes to
> 1) process management code,
> 2) target interfaces, and
> 3) symbol tables.
> Our client would very much like for this work to be incorporated into
> the public GDB sources (although they understand that the decision is
> in the public project's hands), so we'll be posting our design
> thoughts for general discussion. In particular, I believe the
> multi-process work may overlap with some of the work IBM has done to
> support the Cell processor; we'd very much like to work with IBM to
> ensure that the final model is appropriate for both our client and for
> Cell developers.
It looks like the points 1) and 2) you are planning to address
actually do *not* overlap with the work we've been doing on the
Cell combined debugger. The Cell programming model our debugger
supports is bascially a regular multi-threaded model, except that
some threads may execute either PowerPC or SPU architecture code
at any time. Multi-process support is not required.
[ However, of course multi-process support would be a nice *extension*
to the Cell combined debugger, allowing to debug multiple processes,
each of which follows the normal multi-threaded Cell model. ]
Point 3) above would be relevant to the Cell combined debugger as well.
You do not address this point in more detail in your document, but I
assume this would imply introducing the notion of "address spaces" and
associating symbol tables to a particular address space. Something
similar is already needed for the Cell combined debugger, as we have
multiple address spaces even within a single process. I'm definitely
interested in working on adding this support to mainline GDB -- if
that then also helps the multi-process work, that's an additional
benefit.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-11-27 16:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 17:21 Nathan Sidwell
2007-11-20 19:28 ` Nick Roberts
2007-11-20 20:12 ` Jim Blandy
2007-11-21 13:53 ` Michael Snyder
2007-11-26 23:13 ` Jim Blandy
2007-11-27 16:42 ` Ulrich Weigand [this message]
2007-11-30 20:48 ` Thiago Jung Bauermann
2007-12-04 18:17 ` Jim Blandy
2007-12-05 13:41 ` Fabian Cenedese
2007-12-05 20:01 ` Nigel Stephens
2007-11-28 5:18 Pawel Piech
2007-11-29 2:08 ` Nick Roberts
2007-11-29 6:15 ` Pawel Piech
2007-11-29 8:36 ` Vladimir Prus
2007-11-29 16:42 ` Pawel Piech
[not found] ` <474EEB36.1040203@windriver.com>
2007-11-29 16:46 ` Vladimir Prus
2007-11-29 17:36 ` Pawel Piech
2007-11-29 17:51 ` Vladimir Prus
2007-11-29 18:13 ` Pawel Piech
2007-12-04 18:34 ` Jim Blandy
2007-12-04 23:05 ` Pawel Piech
2007-12-05 21:52 ` Jim Blandy
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=200711271642.lARGglTe031746@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=nathan@codesourcery.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