This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
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 options supplied to 'configure' tool:
./configure CFLAGS=-pg CPPFLAGS=-pg --enable-debug
When I recompiled my test MPI application that does MPI_Send and
MPI_Recv with the new library, it generated gmon.out file as expected
(I ran it as 'mpirun -np 2 send_recv'). However, running 'gprof' on
this file didn't provide any information such as the call graphs for
MPI_Send or MPI_Recv. Following is the only function call that I see
in the output:
$ gprof send_recv gmon.out
% cumulative self self total
time seconds seconds calls Ts/call Ts/call name
0.00 0.00 0.00 25 0.00 0.00 data_start
I would like to know if anyone has done something similar with gprof
or any other open source tool with OpenMPI code.
(I found a similar, fairly recent post on the mailing list, but it
seems to talk about profiling the MPI application itself and not the
OpenMPI library routines -
Thanks & Regards,