From: Konstantin Karganov <karganov@gmail.com>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: libGDB and gdbserver questions
Date: Wed, 16 Nov 2005 09:19:00 -0000 [thread overview]
Message-ID: <159126900511160119o24697a0an@mail.gmail.com> (raw)
In-Reply-To: <dlcu2c$ct1$1@sea.gmane.org>
> Then each copy of gdb would connect to a "redirector" you can write, that
> will basically forward all packets to invididual instances of gdbserver.
MPICH already has such wrapper (I was sure it was, but couldn't find
it yesterday...):
It has a "parallel gdb" version called mpigdb:
http://www-unix.mcs.anl.gov/mpi/mpich/docs/userguide/node26.htm#Node29
It wraps the stdio and allows to send gdb commands either to all nodes
or to one specified node. The worst thing is that it works
synchronously - when you issue "step" to one node you can not issue
other commands (even switching to another node) until the step
completes.
As for me, such solution is not suitable even for small MPI programs,
because of process interaction and blocking of the individual steps on
MPI_Recv() and similar.
Anyhow, I don't know the interactive debugger that is capable of
debugging 1000 and more processes.
--
Best regards,
Konstantin.
next prev parent reply other threads:[~2005-11-16 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 12:48 Donny Kurniawan
2005-11-15 14:18 ` Daniel Jacobowitz
2005-11-15 23:45 ` Donny Kurniawan
2005-11-16 0:40 ` Daniel Jacobowitz
2005-11-15 15:34 ` Vladimir Prus
2005-11-15 23:31 ` Donny Kurniawan
2005-11-16 8:01 ` Vladimir Prus
2005-11-17 3:58 ` Daniel Jacobowitz
2005-11-17 18:44 ` Stan Shebs
2005-11-21 8:01 ` Donny Kurniawan
2005-11-16 9:19 ` Konstantin Karganov [this message]
2005-11-21 8:04 ` Donny Kurniawan
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=159126900511160119o24697a0an@mail.gmail.com \
--to=karganov@gmail.com \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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