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 "valgrind <options>" <mpirun-options> ./my_app We will execute "valgrind <options> ./my_app" whenever we start one of your processes. This includes process launched via comm_spawn. HTH Ralph On Nov 16, 2012, at 4:38 PM, Brian Budge <brian.bu...@gmail.com> wrote: > 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 <r...@open-mpi.org> wrote: > Easiest solution: just add valgrind into the cmd line > > mpirun <options> valgrind <valgrind-options> ./my_app > > > On Nov 16, 2012, at 3:37 PM, "Tom Bryan (tombry)" <tom...@cisco.com> 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. > > > > I've never done it, but have you looked at the following FAQs? > > http://www.open-mpi.org/faq/?category=debugging > > > > ---Tom > > > > > > _______________________________________________ > > users mailing list > > us...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/users > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
