[OMPI devel] Repost: MPI_Comm_spawn_multiple() and MPI_ERRORCODES_IGNORE
Repost because I did not see it in the archives after a day.
Rolf Vandevaart wrote On 05/09/06 17:32,:
We believe there is a minor bug in comm_spawn_multiple.c. If a user
hands in an argument of MPI_ERRCODES_IGNORE for the
array_of_errcodes to MPI_Comm_spawn_multiple() and has
parameter checking on, then one will get an error like the
following:
[burl-ct-v440-4:03317] *** MPI_ERR_ARG: invalid argument of some other
kind
[burl-ct-v440-4:03317] *** MPI_ERRORS_ARE_FATAL (goodbye)
I think lines 66-69 need to come out.
if ( NULL == array_of_errcodes ) {
return OMPI_ERRHANDLER_INVOKE(comm, MPI_ERR_ARG,
FUNC_NAME);
}
Looks like this has already been fixed for MPI_Comm_spawn().
Rolf
--
=
rolf.vandeva...@sun.com
781-442-3043
=
[OMPI devel] Non-threaded test fails with thread-safe library
I have built a library with "--enable-mpi-threads --with-threads=posix" (using the trunk) and tried running a simple non-threaded program linked against it. The program just calls to MPI_Send and MPI_Recv so every process sends an MPI_INT to one another. When I run it I see the following: burl-ct-v440-4 86 =>mpirun -np 4 connectivity -v burl-ct-v440-4: checking connection0 <-> 1 burl-ct-v440-4: checking connection1 <-> 2 burl-ct-v440-4: checking connection0 <-> 2 opal_mutex_lock(): Deadlock situation detected/avoided Signal:6 info.si_errno:0(Error 0) si_code:-1() *** End of error message *** burl-ct-v440-4 87 => Since I had the debug enabled, I get to see that one of the processes was trying to grab a lock that it already head.(Nice feature having that error printed out!) Has anyone else seen this? As I said, this is a non-threaded program so there is only one thread per process. I am wondering if I am missing something basic in the building of my library. This test works fine against a library configured without "--enable-mpi-threads --with-threads=posix". Rolf -- = rolf.vandeva...@sun.com 781-442-3043 =
