Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

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.

Subject: Re: [OMPI users] Heap profiling with OpenMPI
From: Ashley Pittman (apittman_at_[hidden])
Date: 2008-08-05 17:06:39

One tip is to use the --log-file=valgrind.out.%
q{OMPI_MCA_ns_nds_vpid} option to valgrind which will name the output
file according to rank. In the 1.3 series the variable has changed from


On Tue, 2008-08-05 at 17:51 +0200, George Bosilca wrote:
> Jan,
> I'm using valgrind with Open MPI on a [very] regular basis and I never
> had any problems. I usually want to know the execution path on the MPI
> applications. For this I use:
> mpirun -np XX valgrind --tool=callgrind -q --log-file=some_file ./my_app
> I just run your example:
> mpirun -np 2 -bynode --mca btl tcp,self valgrind --tool=massif -
> q ./NPmpi -u 4
> and I got 2 non empty files in the current directory:
> bosilca_at_dancer:~/NetPIPE_3.6.2$ ls -l massif.out.*
> -rw------- 1 bosilca bosilca 140451 2008-08-05 11:57 massif.out.
> 21197
> -rw------- 1 bosilca bosilca 131471 2008-08-05 11:57 massif.out.
> 21210
> george.