Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

From: Brian Barrett (brbarret_at_[hidden])
Date: 2006-05-11 02:57:04


Eeeks! That sounds like a bug. Can you attach a debugger and get a
stack trace for the situation where that occurs?

Brian

On May 10, 2006, at 10:17 PM, Rolf Vandevaart wrote:

>
> I have built a library with "--enable-mpi-threads --with-
> threads=posix"
> (using
> the trunk) and tried running a simple non-threaded program linked
> against it.
> The program just calls to MPI_Send and MPI_Recv so every process
> sends an
> MPI_INT to one another.
>
> When I run it I see the following:
>
> burl-ct-v440-4 86 =>mpirun -np 4 connectivity -v
> burl-ct-v440-4: checking connection 0 <-> 1
> burl-ct-v440-4: checking connection 1 <-> 2
> burl-ct-v440-4: checking connection 0 <-> 2
> opal_mutex_lock(): Deadlock situation detected/avoided
> Signal:6 info.si_errno:0(Error 0) si_code:-1()
> *** End of error message ***
> burl-ct-v440-4 87 =>
>
> Since I had the debug enabled, I get to see that one of the processes
> was trying to grab a lock that it already head. (Nice feature
> having
> that error printed out!)
>
> Has anyone else seen this? As I said, this is a non-threaded program
> so there is only one thread per process. I am wondering if I am
> missing
> something basic in the building of my library. This test works
> fine against
> a library configured without "--enable-mpi-threads --with-
> threads=posix".
>
> Rolf
>
>
>
>
>
>
>
> --
>
> =========================
> rolf.vandevaart_at_[hidden]
> 781-442-3043
> =========================
>
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/devel