From: Fred Fish <fnf@specifix.com>
To: gdb@sourceware.org
Subject: Multi process debugging using gdb - references?
Date: Mon, 26 Mar 2007 14:39:00 -0000 [thread overview]
Message-ID: <200703260739.13463.fnf@specifix.com> (raw)
I'm curious about the status of using gdb to debug multiple processes.
I've read most of the past messages I could find by doing a search on
"multiprocess" and "multi process" so I know about the recent work to
support multiple processes that share the same executable file, such
as following forked processes.
What I'm more interested in is being able to control and debug
multiple processes that don't share the same executable, may not even
be running on the same machine, and may not be running on machines of
the same architecture.
My gut feeling says that using some front end to control multiple
instances of gdb is probably a better solution than trying to enhance
gdb to handle this using a single gdb process.
Also, any pointers/references to published papers on multi process
debugging, other debuggers that implement multi process debugging
(such as Totalview), works in progress, etc, would be appreciated.
-Fred
next reply other threads:[~2007-03-26 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 14:39 Fred Fish [this message]
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
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=200703260739.13463.fnf@specifix.com \
--to=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