Thanks Gilles,I’ve tried using these options but still cannot get the trace in the source code.
— Murali From: devel <devel-boun...@lists.open-mpi.org<mailto:devel-boun...@lists.open-mpi.org>> on behalf of Gilles Gouaillardet <gilles.gouaillar...@gmail.com<mailto:gilles.gouaillar...@gmail.com>> Reply-To: Open MPI Developers <devel@lists.open-mpi.org<mailto:devel@lists.open-mpi.org>> Date: Wednesday, September 28, 2016 at 3:22 PM To: Open MPI Developers <devel@lists.open-mpi.org<mailto:devel@lists.open-mpi.org>> Subject: Re: [OMPI devel] Memory trace using valgrind in OpenMPI 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 <ema...@llnl.gov<mailto:ema...@llnl.gov>> 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 <valgrind-options> ./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
