MPI_Errhandler_c2f( MPI_ERRHANDLER_NULL ) and
MPI_Info_c2f( MPI_INFO_NULL ) have the same problem as well.
On Tue, 2 Aug 2005, Anthony Chan wrote:
>
> With lam712b22, the following program caught signal 11 with any of
> MPI_XXX_c2f( MPI_XXX_NULL ).
>
> *****************************************************************
> #include <stdio.h>
> #include "mpi.h"
>
> int main( int argc, char *argv[] )
> {
> MPI_Fint f_handle;
>
> MPI_Init( &argc, &argv );
>
> f_handle = MPI_Comm_c2f( MPI_COMM_NULL );
> /* f_handle = MPI_Group_c2f( MPI_GROUP_NULL ); */
> /* f_handle = MPI_Request_c2f( MPI_REQUEST_NULL ); */
> /* f_handle = MPI_Type_c2f( MPI_DATATYPE_NULL ); */
> /* f_handle = MPI_Op_c2f( MPI_OP_NULL ); */
> printf( "f_handle = %d\n", f_handle );
>
> MPI_Finalize();
> return( 0 );
> }
> ********************************************************************
> The output of mpiexec -n 1 a.out is
>
> mpiexec -n 1 ts_objc2f
> -----------------------------------------------------------------------------
> One of the processes started by mpirun has exited with a nonzero exit
> code. This typically indicates that the process finished in error.
> If your process did not finish in error, be sure to include a "return
> 0" or "exit(0)" in your C code before exiting the application.
>
> PID 32234 failed on node n0 (127.0.0.1) due to signal 11.
> -----------------------------------------------------------------------------
> mpirun failed with exit status 11.
> ********************************************************************
>
> If the problem has been fixed in the latest release, please let me know.
>
> Thanks,
> A.Chan
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
>
|
