You should be able to just run valgrind on your application. Just execute your
job with:
mpirun valgrind
On Dec 18, 2011, at 11:27 AM, Mudassar Majeed wrote:
> Dear people,
> I am using MPI over a supercomputing center. I don't
> have access to install OpenMPI again
Dear people,
I am using MPI over a supercomputing center. I don't have
access to install OpenMPI again with enabling valgrind. I need to check the
memory leaks in my application. How can I see in which line of my code of MPI
application there is memory leak ??? Supercomput
Hmm. I'm unfortunately unable to replicate your results -- I get the
same valgrind output with your test program regardless of whether I
use gfortran or mpif90 (i.e., it shows the lost block). :-\
FWIW, I'm using RHEL4U4 (and U6) with gfortran 4.1.0 and Valgrind 3.4.0.
On Feb 14, 2009, at
On Thursday 12 February 2009 4:30:27 pm George Bosilca wrote:
> Some of the configure options changed their name for the 1.3. Here is
> the updated list you should use in order to get valgrind support for
> the 1.3:
>
> --enable-memchecker --with-valgrind --with-memory-manager=none
>
>george.
Hi,
please note, that for plain standard valgrind runs (without ompi-internal
checks), You will not need to turn on the v1.3 options --enable-memchecker.
However, if You do, access to buffers, some MPI-standard conformance and (if
You select so) defined-ness checks of ompi-structures will be ena
On Feb 12, 2009, at 1:30 PM, George Bosilca wrote:
Some of the configure options changed their name for the 1.3. Here
is the updated list you should use in order to get valgrind support
for the 1.3:
--enable-memchecker --with-valgrind --with-memory-manager=none
Note that --enable-memcheck
Some of the configure options changed their name for the 1.3. Here is
the updated list you should use in order to get valgrind support for
the 1.3:
--enable-memchecker --with-valgrind --with-memory-manager=none
george.
On Feb 12, 2009, at 16:23 , Reuben D. Budiardja wrote:
On Thursday 1
On Feb 12, 2009, at 1:23 PM, Reuben D. Budiardja wrote:
From memory and reading the above links (i.e. untested advice):
1) Use OpenMPI 1.3 where the default is not to include this.
I tried it with OpenMPI 1.3, I didn't give any configure option
except --prefix, and Valgrind still does not work
On Thursday 12 February 2009 11:50:07 am Ashley Pittman wrote:
>
> > I am using OpenMPI-1.2.8 with all the default configure option. What
> > should I
> > do to be able use Valgrind with program compiled by OpenMPI ?
>
> From memory and reading the above links (i.e. untested advice):
> 1) Use Open
On 12 Feb 2009, at 15:53, Reuben D. Budiardja wrote:
Hello,
I am having problem that if a program is compiled with OpenMPI,
Valgrind
doesn't work correctly, i.e: it does not show the memory leak like it
supposed too. The same test program compiled with regular "gfortran"
and run
under Valgri
Hello,
I am having problem that if a program is compiled with OpenMPI, Valgrind
doesn't work correctly, i.e: it does not show the memory leak like it
supposed too. The same test program compiled with regular "gfortran" and run
under Valgrind will show the memory leak.
I search the list archive
11 matches
Mail list logo
