So the application procs are all gone, but mpiexec isn’t exiting? I’d suggest running valgrind, given the corruption.
> On Jun 30, 2016, at 10:21 AM, Orion Poplawski <or...@cora.nwra.com> wrote: > > On 06/30/2016 10:33 AM, Orion Poplawski wrote: >> No, just mpiexec is running. single node. Only see it when the test is >> executed with "make check", not seeing it if I just run mpiexec -n 6 >> ./testphdf5 by hand. > > > Hmm, now I'm seeing it running mpiexec by hand. Trying to check it via gdb > indicates a corrupted stack: > > > (gdb) bt > #0 0xb6cd8ac4 in poll () from /lib/libc.so.6 > #1 0x00000000 in ?? () > Backtrace stopped: previous frame identical to this frame (corrupt stack?) > > Any other tracing I can turn on? > > -- > Orion Poplawski > Technical Manager 303-415-9701 x222 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane or...@nwra.com > Boulder, CO 80301 http://www.nwra.com > _______________________________________________ > users mailing list > us...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2016/06/29578.php
