[MPICH] about MPI_Comm_spawn
David Ashton
ashton at mcs.anl.gov
Fri Sep 23 23:05:56 CDT 2005
If you feel you've compiled good code, linked with the MPICH2 libraries and
run the job correctly with mpiexec then I would re-compile the application
with the Debug options turned on and then run the job like this:
"mpiexec -localonly 1 spawn1.exe"
If the application crashes you will be able to connect the debugger to it
and determine where the program crashed.
-David Ashton
-----Original Message-----
From: llwaeva at 21cn.com [mailto:llwaeva at 21cn.com]
Sent: Friday, September 23, 2005 9:21 PM
To: David Ashton; mpich
Subject: RE: [MPICH] about MPI_Comm_spawn
> Under Windows, any MPI application that calls MPI_Comm_spawn must be
started
> by mpiexec. If you run "myapp.exe" instead of "mpiexec -n 1 myapp.exe"
you
> will not be able to call the spawn functions.
> -David Ashton
I also try to use
mpiexec -n 1 spawn1.exe
but still get
Error encountered before initializing MPICH
job aborted:
rank: node: exit code[: error message]
0: rex: 1: process 0 exited without calling finalize
More information about the mpich-discuss
mailing list