Hi Joao,
Thanks for the bug report! You do not have to call free/disconnect
before MPI_Finalize. If you do not, they will be called automatically.
Unfortunately, there was a bug in the code that did the free/disconnect
automatically. This is fixed in r18079.
Thanks again,
Tim
Joao Vicente
Hi again,
when I call MPI_Init_thread in the same program the error is:
spawning ...
opal_mutex_lock(): Resource deadlock avoided
[localhost:07566] *** Process received signal ***
[localhost:07566] Signal: Aborted (6)
[localhost:07566] Signal code: (-6)
[localhost:07566] [ 0] /lib/libpthread.so.0
Really MPI_Finalize is crashing and calling MPI_Comm_{free,disconnect} works!
I don't know if the free/disconnect must appear before a MPI_Finalize
for this case (spawn processes) some suggest ?
I use loops in spawn:
- first for testing :)
- and second because certain MPI applications don't
On 30/03/2008, Joao Vicente Lima wrote:
> Hi,
> sorry bring this again ... but i hope use spawn in ompi someday :-D
I believe it's crashing in MPI_Finalize because you have not closed
all communication paths between the parent and the child processes.
For the parent process, try calling MPI_Comm
My C++ is a little rusty. Is that returned intercommunicator going
where you think it is? If you unroll the loop does the same badness
happen?
On Mon, 2008-03-31 at 02:41 -0300, Joao Vicente Lima wrote:
> Hi,
> sorry bring this again ... but i hope use spawn in ompi someday :-D
>
> The executi
