[petsc-users] SlepcInitialize not return

Barry Smith bsmith at mcs.anl.gov
Fri May 16 19:54:52 CDT 2014


  Sounds like some issue with how you are using the shared libraries. If you don’t show us the offending code it is going to be awfully difficult for us to debug it.

  Barry

On May 16, 2014, at 6:39 PM, 张国熙 <altriaex86 at gmail.com> wrote:

> execute program A calls .so library B, and .so libraryB calls SLEPclibrary.
> I used to put MPI_Init() only in A. But this time I try to put it in A,B( and C).
> Now it returns to this to me.
> I guess maybe this is why it does not return. However I don't know how to fix it.
> 
> INTERNAL ERROR: Invalid error class (59) encountered while returning from
> MPI_Init.  Please file a bug report.
> Fatal error in MPI_Init: Unknown error.  Please file a bug report., error stack:
> (unknown)(): unable to bind socket to port
> INTERNAL ERROR: Invalid error class (59) encountered while returning from
> MPI_Init.  Please file a bug report.
> Fatal error in MPI_Init: Unknown error.  Please file a bug report., error stack:
> (unknown)(): unable to bind socket to port
> [cli_1]: aborting job:
> Fatal error in MPI_Init: Unknown error.  Please file a bug report., error stack:
> (unknown)(): unable to bind socket to port
> INTERNAL ERROR: Invalid error class (59) encountered while returning from
> MPI_Init.  Please file a bug report.
> INTERNAL ERROR: Invalid error class (59) encountered while returning from
> MPI_Init.  Please file a bug report.
> Fatal error in MPI_Init: Unknown error.  Please file a bug report., error stack:
> (unknown)(): unable to bind socket to port
> [cli_3]: aborting job:
> Fatal error in MPI_Init: Unknown error.  Please file a bug report., error stack:
> (unknown)(): unable to bind socket to port
> [cli_0]: aborting job:
> Fatal error in MPI_Init: Unknown error.  Please file a bug report., error stack:
> (unknown)(): unable to bind socket to port
> Fatal error in MPI_Init: Unknown error.  Please file a bug report., error stack:
> (unknown)(): unable to bind socket to port
> [cli_2]: aborting job:
> Fatal error in MPI_Init: Unknown error.  Please file a bug report., error stack:
> (unknown)(): unable to bind socket to port
> 
> 
> 
> 2014-05-17 9:28 GMT+10:00 Barry Smith <bsmith at mcs.anl.gov>:
> 
>    Reproduce this in a small about of code (sounds easy in this case) and then email the code out; your verbal descriptions is not detailed enough to determine the problem. Also send a make file that links the .so library, it could be a problem related to that.
> 
>    Barry
> 
> On May 16, 2014, at 6:21 PM, 张国熙 <altriaex86 at gmail.com> wrote:
> 
> > Hi,
> >
> > I write a piece of code containing SLEPc calling and compile it into a .so library. Then I call this library in my program. I call MPI_Init in the main program, but it turns out that function SlepcInitialize in SLEPc .so library will not return, and the program stuck at that line. I don't know if this problem related to the place of MPI_Init calling, but the library works well if I only use one process and not initialize MPI outside.
> >
> > Guoxi
> 
> 



More information about the petsc-users mailing list