As developer of BLCR (used for checkpointing in OMPI) I am currently
working on some changes for the next release (about 6 months away) that
could accidentally break usage of the BLCR library as a dynamically
opened object. I know that at least once in the past, changes I made
broke dlopen() u
On Tue, Sep 18, 2007 at 10:57:38AM -0400, George Bosilca wrote:
> More information about this can be founded in the trac #1127
> (https://svn.open-mpi.org/trac/ompi/ticket/1127).
>
OK. So the code I cited is only a temporary solution. Thanks.
> george.
>
> On Sep 18, 2007, at 10:20 AM, Gleb Nata
More information about this can be founded in the trac #1127
(https://svn.open-mpi.org/trac/ompi/ticket/1127).
george.
On Sep 18, 2007, at 10:20 AM, Gleb Natapov wrote:
On Tue, Sep 18, 2007 at 09:44:42AM -0400, George Bosilca wrote:
The setup of a communicators include as a last stage, a co
On Tue, Sep 18, 2007 at 09:44:42AM -0400, George Bosilca wrote:
> The setup of a communicators include as a last stage, a collective
> communication. As a result, some of the nodes can exit the collective
> before the others and therefore can start sending messages using this
> communicator [whi
The setup of a communicators include as a last stage, a collective
communication. As a result, some of the nodes can exit the collective
before the others and therefore can start sending messages using this
communicator [while some of the other nodes are still waiting for the
collective com
George,
In the comment you are saying that "a message for a not yet existing
communicator can happen". Can you explain in what situation it can
happen?
Thanks,
--
Gleb.
