I attach with gdb on the processes and do a "call mca_pml_ob1_dump(comm, 1)". This allows the debugger to make a call our function, and output internal information about the library status.
George. On Thu, Apr 5, 2018 at 4:03 PM, Noam Bernstein <noam.bernst...@nrl.navy.mil> wrote: > On Apr 5, 2018, at 3:55 PM, George Bosilca <bosi...@icl.utk.edu> wrote: > > Noam, > > The OB1 provide a mechanism to dump all pending communications in a > particular communicator. To do this I usually call mca_pml_ob1_dump(comm, > 1), with comm being the MPI_Comm and 1 being the verbose mode. I have no > idea how you can find the pointer to the communicator out of your code, but > if you compile OMPI in debug mode you will see it as an argument to the > mca_pml_ob1_send > and mca_pml_ob1_recv function. > > This information will give us a better idea on what happened to the > message, where is has been sent (or not), and what were the source and tag > used for the matching. > > > Interesting. How would you do this in a hung program? Call it before you > call the things that you expect will hang? And any ideas how to get a > communicator pointer from fortran? > > Noam > > > > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/users >
_______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
