fixed in r21952
thanks.
On Tue, Sep 8, 2009 at 5:08 PM, Arthur Huillet wrote:
> Lenny Verkhovsky wrote:
>
>> Why not using __FUNCTION__ in all our error messages ???
>>
>
> Sounds good, this way the function names are always correct.
>
> --
> Greetings, A. Huillet
>
> ___
Lenny Verkhovsky wrote:
Why not using __FUNCTION__ in all our error messages ???
Sounds good, this way the function names are always correct.
--
Greetings,
A. Huillet
Why not using __FUNCTION__ in all our error messages ???
diff -r 686ec286164a ompi/communicator/communicator.h
--- a/ompi/communicator/communicator.h Tue Sep 08 14:39:03 2009 +0200
+++ b/ompi/communicator/communicator.h Tue Sep 08 15:48:06 2009 +0200
@@ -313,7 +313,7 @@
{
#if OPAL_ENABLE_DEBUG
Hi,
please find attached a patch to ompi/communicator/communicator.h that
fixes the error message displayed by ompi_comm_peer_lookup() so the
function name that appears is correct.
--
Greetings,
A. Huillet
diff -r 686ec286164a ompi/communicator/communicator.h
--- a/ompi/communicator/commun
Hi,
I'm working on r21949 of the trunk.
When I run on a single node with 4 processes this simple program calling
2 times MPI_Comm_dup , the processes hang from time to time in the 2nd dup.
int main(int argc, char *argv[])
{
MPI_Comm comm,comm2;
MPI_Init(&argc, &argv);
MPI_Comm_dup(MPI_CO
