Hi All,
I am trying to profile (get the call graph/call sequence of) Open MPI
communication routines using GNU Profiler (gprof) since the
communication calls are implemented using macros and it's harder to
trace them statically. In order to do that I compiled the OpenMPI
source code with following
OK, it turned out to be a really stupid mistake.
Sorry for spamming and thanks for the help!
Regards,
Aniruddha
On Mon, Sep 28, 2009 at 11:28 AM, Aniruddha Marathe <
marathe.anirud...@gmail.com> wrote:
> Hi Jeff,
>
> Thanks for the pointers. I tried with both CFLAGS=-g3 and
if I "break MPI_Barrier" (for example). We actually
> have a "--enable-debug" option to OMPI's configure, but it does turn on a
> bunch of other debugging code that will definitely result in performance
> degradation at run-time (one of its side effects is to add &qu
Hello,
I am new to OpenMPI library and I am trying to step through common MPI
communication calls using gdb. I attach gdb to one of the processes
(using the steps mentioned on the OpenMPI Debugging FAQ page) and set
a breakpoint on 'MPI_Barrier' and expect gdb to jump into the
definition of MPI_Ba
