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
What I am trying to acheive in this simplified code is:
- 2 types of processes (root, and children, ids/rank = 10 and 0-9
respectively)
- init:
- root will listen to children "completed"
- children will listen to root notification when all has completed
- while there is no
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
Hi, Simon,
The pairwise algorithm passes messages in a synchronised ring-like fashion
with increasing stride, so it works best when independent communication
paths could be established between several ports of the network
switch/router. Some 1 Gbps Ethernet equipment is not capable of doing so,
so
First cygwin 1.6.3-3 version of packages
libopenmpi
libopenmpi-devel
openmpi
are available in the Cygwin distribution:
CHANGES
Initial cygwin package.
This is based on mainstream release 1.6.3 plus
https://svn.open-mpi.org/trac/ompi/ticket/3371
Full upstream changes:
http://www.open-
On 11/15/2012 11:57 PM, John Marshall wrote:
Hi,
I'm trying to figure out how I can specify my own launch agent.
This is what I'd like to be able to do:
* have rsh/ssh calling semantics
* specify a full path for the launch agent
* use an environment variable to specify the launch agent
