Re: [OMPI users] Crash during MPI_Finalize

2016-10-14 Thread George Reeke
On Tue, 2016-10-11 at 10:10 +0900, Gilles Gouaillardet wrote: > George, > at first, i recommend you try the latest v1.10 (1.10.4) or event > 2.0.1. > Dear Gilles et al, Can this coexist with the version of open-mpi on my RedHat system (1.10.2)? Is this a matter of downloading source and

Re: [OMPI users] Crash during MPI_Finalize

2016-10-11 Thread Jeff Squyres (jsquyres)
On Oct 11, 2016, at 8:58 AM, George Reeke wrote: > > George B. et al, > --Is it normal to top-post on this list? I am following your > example but other lists I am on prefer bottom-posting. Stylistic note: we do both on this list. Specifically: there's no

Re: [OMPI users] Crash during MPI_Finalize

2016-10-11 Thread George Reeke
George B. et al, --Is it normal to top-post on this list? I am following your example but other lists I am on prefer bottom-posting. --I attach the complete code of the andmsg program, as it is quite short (some bits removed for brevity and I have omitted my headers and startup function

Re: [OMPI users] Crash during MPI_Finalize

2016-10-10 Thread George Bosilca
George, There is too much information missing from your example. If I try to run the code on the top assuming the process is is_host(NC.node), I have on NC.commd 3 communications (ignore the others): rc = MPI_Send(, 1, MPI_INT, NC.dmsgid, SHUTDOWN_ANDMSG, NC.commd); MPI_Recv(, 1, MPI_INT,

Re: [OMPI users] Crash during MPI_Finalize

2016-10-10 Thread Gilles Gouaillardet
George, i tried to mimick this with the latest v1.10, and failed to reproduce the error. at first, i recommend you try the latest v1.10 (1.10.4) or event 2.0.1. unusable stack trace can sometimes be caused by unloaded modules, so if the issue persists, you might want to try rebuilding

[OMPI users] Crash during MPI_Finalize

2016-10-06 Thread George Reeke
Dear colleagues, I have a parallel MPI application written in C that works normally in a serial version and in the parallel version in the sense that all numerical output is correct. When it tries to shut down, it gives the following console error messsage: Primary job terminated normally, but