Ah, I see. I just made an environment variable check to run valgrind from
the spawn and it works great. Your solution below is nice and
non-intrusive. I'll keep it in mind for the future.
Thanks,
Brian
On Fri, Nov 16, 2012 at 7:05 PM, Ralph Castain wrote:
> Actually, silly me. I didn't ful
Actually, silly me. I didn't fully grok your note to see that you wanted to run
valgrind on slaves generated via comm_spawn.
That's a tad trickier, but not too hard to do. There actually is a "fork agent"
you can define that will do what you want. If you do this:
mpirun -mca orte_fork_agent "va
Thanks very much Ralph. Silly me I thought it might actually be some
effort :)
Brian
On Fri, Nov 16, 2012 at 4:04 PM, Ralph Castain wrote:
> Easiest solution: just add valgrind into the cmd line
>
> mpirun valgrind ./my_app
>
>
> On Nov 16, 2012, at 3:37 PM, "Tom Bryan (tombry)"
> wrote:
Easiest solution: just add valgrind into the cmd line
mpirun valgrind ./my_app
On Nov 16, 2012, at 3:37 PM, "Tom Bryan (tombry)" wrote:
>> If I want to run valgrind on my processes, what steps should be
>> taken? I'm currently more interested in running valgrind on the
>> slave processes.
>
> If I want to run valgrind on my processes, what steps should be
> taken? I'm currently more interested in running valgrind on the
> slave processes.
I've never done it, but have you looked at the following FAQs?
http://www.open-mpi.org/faq/?category=debugging
---Tom
Hi all -
I'm using openmpi to spawn child processes in singleton mode. If I use
mpirun, I can just run
> mpirun valgrind myprog
With spawn, it is expected that the spawned process will call
mpi_init(_thread). If I want to run valgrind on my processes, what steps
should be taken? I'm currently
