[mpich-discuss] Using an Alternative Debugger for MPICH

[Yauheni Zelenko]

Hi, Ellis!

If you open to proprietary alternatives, I could recommend DDT by Allinea. I use it too.

Eugene.
________________________________________
From: mpich-discuss-bounces at mcs.anl.gov [mpich-discuss-bounces at mcs.anl.gov] On Behalf Of Ellis H. Wilson III [ellis at runnersroll.com]
Sent: Friday, April 01, 2011 11:21 AM
To: mpich-discuss at mcs.anl.gov
Subject: [mpich-discuss] Using an Alternative Debugger for MPICH

Hi All,

I'm interested in using a custom debugger to debug an mpi program of
mine.  From past reading I had thought that the option -dbg=<debugger>
would allow me to use my own mpirun_dbg.<debugger> to debug a program,
but that option seems to be missing from mpich2 implementations or I am
configuring it incorrectly.  I've configured, compiled and installed
mpich2-1.3.1 with the following options:

./configure --with-file-system="pvfs2+nfs+ufs" --enable-romio
--enable-mpe --enable-g --prefix=~/usr

And though I can verify it runs fine without the -dbg parameter, when I
use such I am getting the following error message:

[mpiexec at ...] match_arg (./utils/args/args.c:122): unrecognized argument dbg
[mpiexec at ...] HYDU_parse_array (./utils/args/args.c:140): argument
matching returned error
[mpiexec at ...] HYD_uii_mpx_get_parameters (./ui/mpich/utils.c:1033):
error parsing input array

So I assume dbg is gone, but I cannot find out what a replacement for it
is, if any exist.  Any suggestions are greatly appreciated.

Best,

ellis
_______________________________________________
mpich-discuss mailing list
mpich-discuss at mcs.anl.gov
https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss