Hi Edgard,
just to tell that I tested your fixe that has been merged into
ompi-release/v2.x (9ba667815) and it works! :)
Thanks!
Eric
On 12/07/16 04:30 PM, Edgar Gabriel wrote:
I think the decision was made to postpone the patch to 2.0.1, since the
release of 2.0.0 is eminent.
Thanks
Edgar
Hi,
has someone tried OpenMPI 2.0 with Petsc 3.7.2?
I am having some errors with petsc, maybe someone have them too?
Here are the configure logs for PETSc:
http://www.giref.ulaval.ca/~cmpgiref/dernier_ompi/2016.07.25.01h16m02s_configure.log
http://www.giref.ulaval.ca/~cmpgiref/dernier_ompi/20
Ok,
here is the 2 points answered:
#1) got valgrind output... here is the fatal free operation:
==107156== Invalid free() / delete / delete[] / realloc()
==107156==at 0x4C2A37C: free (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==107156==by 0x1E63CD5F: opal_free (malloc.
Folks,
This is a followup of a thread that initially started at
http://www.open-mpi.org/community/lists/users/2016/07/29635.php
The user is trying to build Open MPI with PGI compiler and
libslurm.la/libpmi.la support, and slurm was built with gcc compiler.
At first, it fails because the
Gilles,
My initial thought is that libslurm probably does require linking
libpthread, either for for linking pthread_* symbols, or for proper
*operation* (such as thread-safe versions of functions which override weak
definitions in libc).
If so, then neither omitting "-pthread" nor telling pgcc n
Paul,
in my environment, libslurm.la contains
# Linker flags that can not go in dependency_libs.
inherited_linker_flags=' -pthread'
# Libraries that this one depends upon.
dependency_libs=' -ldl -lpthread'
so bottom line, it invokes the compiler with both -pthread and -lpthread
iirc, -pthre
Eric,
where can your test case be downloaded ? how many nodes and tasks do you
need to reproduce the bug ?
fwiw, currently there are two Open MPI repositories
- https://github.com/open-mpi/ompi
there is only one branch and is the 'master' branch, today, this can
be seen as Open MPI 3.0 pre
It looks to me like double free on both send and receive requests. The receive
free is an extra OBJ_RELEASE of MPI_DOUBLE which was not malloced (invalid
free). The send free is an assert failure in OBJ_RELEASE of an OBJ_NEW() object
(invalid magic). I plan to look at in in the next couple of da