Re: [OMPI devel] Memory trace using valgrind in OpenMPI

[Gilles Gouaillardet]

Hi,

you might want to rebuild Open MPI with the previous configure command
line, and append
--disable-dlopen CFLAGS='-g -O0'

by default, components are built into their own lib (for example
mca_btl_tcp.so) which is dlopen'ed and dlclose'd at runtime, and that might
not be supported by post mortem tools

Cheers,

Gilles

On Thursday, September 29, 2016, Emani, Murali  wrote:

> Hi all,
>
> I am trying to perform memory allocation analysis in OpenMPI using
> *valgrind* and use *addr2line* to get the location in the source code in
> the application and the library.
>
> I have compiled OpenMPI with valgrind using
>
> ./configure —prefix=<*path>* —enable-debug —enable-mem-debug
> —enable-memchecker —with-valgrind=/*path-to-valgrind*/
>
> I compile and run the sample code, myapp.c as
> mpicc –g myapp.c –o myapp
> mpirun –np <*num_processes*> valgrind ** ./myapp
>
> The valgrind output yields hex codes and I try to retrieve the line in the
> source code using *addr2line. *This  yields the exact line in the source
> code of myapp.c but not in OpenMPI source.  I was expecting it to get the
> exact location and line numbers in OpenMPI too as it is compiled with debug
> info enabled.
>
> Can someone provide any pointers if this is the correct way or/and how to
> achieve this?
>
> —
> Murali
>
>
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] OSHMEM and shmem_ptr

[Pavel Shamis]

Nick,

IMHO, the major issue here is the support for "static" data objects.
This requirement gets directly translated to the XPMEM support for the
platform, otherwise it is very challenging to get it implement.
OpenMPI/OSHMEM provides support for xpmem (actually there is more than
one transport), but you have to make sure that the underlaying system
has the XPMEM kernel module installed. There is an open source version
of XPMEM (https://github.com/hjelmn/xpmem) which went through numerous
updates and bugfixes during the last year, even so it is not a
formally "QA"ed product.

-Pasha
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

[OMPI devel] Memory trace using valgrind in OpenMPI

[Emani, Murali]

Hi all,

I am trying to perform memory allocation analysis in OpenMPI using valgrind and 
use addr2line to get the location in the source code in the application and the 
library.

I have compiled OpenMPI with valgrind using

./configure —prefix= —enable-debug —enable-mem-debug —enable-memchecker 
—with-valgrind=/path-to-valgrind/

I compile and run the sample code, myapp.c as
mpicc –g myapp.c –o myapp
mpirun –np  valgrind  ./myapp

The valgrind output yields hex codes and I try to retrieve the line in the 
source code using addr2line. This  yields the exact line in the source code of 
myapp.c but not in OpenMPI source.  I was expecting it to get the exact 
location and line numbers in OpenMPI too as it is compiled with debug info 
enabled.

Can someone provide any pointers if this is the correct way or/and how to 
achieve this?

—
Murali

___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel