This routine does make sends and receives of length zero; this is legal in MPI but possibly Open-MPI has bugs dealing with this.
Barry On Fri, 19 Jan 2007, Berend van Wachem wrote: > Hi, > > valgrind shows something related to open-mpi, see below. I'll try mpich > to see if the problem goes away. > > Thanks, > Berend. > > > ==3683== Syscall param writev(vector[...]) points to uninitialised > byte(s) > ==3683== at 0x543A607: writev (in /lib64/tls/libc-2.3.6.so) > ==3683== by 0x5BE0AEA: mca_oob_tcp_msg_send_handler > (in /usr/local/lib/openmp > > > i/mca_oob_tcp.so) > ==3683== by 0x5BE1827: mca_oob_tcp_peer_send > (in /usr/local/lib/openmpi/mca_o > > > ob_tcp.so) > ==3683== by 0x5BE5B93: mca_oob_tcp_send_nb > (in /usr/local/lib/openmpi/mca_oob > > > _tcp.so) > ==3683== by 0x4B47DBD: _orte_iof_base_frag_ack > (in /usr/local/lib/liborte.so. > > > 0.0.0) > ==3683== by 0x4B47639: orte_iof_base_endpoint_forward > (in /usr/local/lib/libo > > > rte.so.0.0.0) > ==3683== by 0x6D45538: orte_iof_svc_proxy_recv > (in /usr/local/lib/openmpi/mca > > > _iof_svc.so) > ==3683== by 0x5BE137A: mca_oob_tcp_msg_recv_complete > (in /usr/local/lib/openm > > > pi/mca_oob_tcp.so) > ==3683== by 0x5BE2D18: mca_oob_tcp_peer_recv_handler > (in /usr/local/lib/openm > > > pi/mca_oob_tcp.so) > ==3683== by 0x4C7E466: opal_event_loop > (in /usr/local/lib/libopal.so.0.0.0) > ==3683== by 0x4C78A55: opal_progress > (in /usr/local/lib/libopal.so.0.0.0) > ==3683== by 0x4030AF: opal_condition_wait (condition.h:81) > ==3683== Address 0x41CF348 is not stack'd, malloc'd or (recently) > free'd > >
