Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: [OMPI devel] some possible bugs after trying 1.2.6
From: Lisandro Dalcin (dalcinl_at_[hidden])
Date: 2008-04-14 17:24:52


Hi all, I've just downloaded and installed release 1.2.6.
Additionally, I'm reimplementing from scratch my Python wrappers for
MPI using some more advanded tools than manual C coding. Now, I do not
try in any way of doing argument checking as I did before. Then I've
ran al my unittest machinger. And then comments follows.

MPI_Comm_get_errhandler() if called with MPI_COMM_NULL raises error
class MPI_ERR_ARG. I believe it should be MPI_ERR_COMM.

MPI_Abort() if called with MPI_COMM_NULL directly abort the process
instead of calling the error handler set in MPI_COMM_WORLD. I do not
know what is correct here; this is just for your information.

MPI_Cancel() and MPI_Request_free() success if they are called with
MPI_REQUEST_NULL. At first sight, this seems erroneous (at least in
the MPI-1) as TestXXX and WaitXXX should be the only accepting the
null handle, but now I cannot remember if MPI-2 clarified/modified
this (I believe not).

-- 
Lisandro Dalcín
---------------
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594