From: Michael Snyder <Michael.Snyder@palmsource.com>
To: fnf@specifix.com
Cc: gdb@sourceware.org
Subject: Re: Multi process debugging using gdb - references?
Date: Mon, 26 Mar 2007 22:13:00 -0000 [thread overview]
Message-ID: <1174946671.24110.52.camel@localhost.localdomain> (raw)
In-Reply-To: <1174945438.24110.48.camel@localhost.localdomain>
On Mon, 2007-03-26 at 14:43 -0700, Michael Snyder wrote:
> On Mon, 2007-03-26 at 07:39 -0700, Fred Fish wrote:
> > I'm curious about the status of using gdb to debug multiple processes.
> >
>
> I used to know about a project that did as you suggest -- use a
> front end to control multiple gdbs. Let me see if I can dredge
> up the memory.
>
Fred, google up "P2D2", by Robert Hood (he was at NASA at the
time, don't know if he still is). Here's one reference:
http://www.dl.ac.uk/TCSC/Subjects/Parallel_Algorithms/tools_survey/node37.html
prev parent reply other threads:[~2007-03-26 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 14:39 Fred Fish
2007-03-26 14:51 ` Daniel Jacobowitz
2007-03-26 15:54 ` Gary Funck
[not found] ` <1174945438.24110.48.camel@localhost.localdomain>
2007-03-26 22:13 ` Michael Snyder [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=1174946671.24110.52.camel@localhost.localdomain \
--to=michael.snyder@palmsource.com \
--cc=fnf@specifix.com \
--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