Per Satish's last mail
(http://www.open-mpi.org/community/lists/users/2015/04/26823.php), George is
looking at a followup issue...
> On Apr 30, 2015, at 2:57 PM, Ralph Castain wrote:
>
> Thanks! The patch wasn’t quite correct, but we have a good one now and it is
> going into 1.8.5 (just squ
Thanks! The patch wasn’t quite correct, but we have a good one now and it is
going into 1.8.5 (just squeaked in before release)
> On Apr 29, 2015, at 9:50 PM, Satish Balay wrote:
>
> OpenMPI developers,
>
> We've had issues (memory errors) with OpenMPI - and code in PETSc
> library that uses M
Thank you!
George reviewed your patch and adjusted it a bit. We applied it to master and
it's pending to the release series (v1.8.x).
Would you mind testing a nightly master snapshot? It should be in tonight's
build:
http://www.open-mpi.org/nightly/master/
> On Apr 30, 2015, at 12:50
OpenMPI developers,
We've had issues (memory errors) with OpenMPI - and code in PETSc
library that uses MPI_Win_fence().
Vagrind shows memory corruption deep inside OpenMPI function stack.
I'm attaching a potential patch that appears to fix this issue for us.
[the corresponding valgrind trace is
