Re: [OMPI users] MPI_ERR_TRUNCATE with MPI_Revc without Infinipath

2008-08-21 Thread Tom Riddle
limited number of hosts, it seems to behave as expected.  Thanks!! Tom --- On Mon, 8/18/08, George Bosilca wrote: From: George Bosilca Subject: Re: [OMPI users] MPI_ERR_TRUNCATE with MPI_Revc without Infinipath To: "Open MPI Users" Cc: "Tom Riddle" List-Post: users@lis

Re: [OMPI users] MPI_ERR_TRUNCATE with MPI_Revc without Infinipath

2008-08-18 Thread Tom Riddle
ATE error messages. I'm using the latest version of Open MPI (1.4a1r19313). There was a bug that might be related to your problem but our commit log shows it was fixed by commit 18830 on July 9. george. On Aug 13, 2008, at 5:49 PM, Tom Riddle wrote: > Hi, > > A bit more info

Re: [OMPI users] MPI_ERR_TRUNCATE with MPI_Revc without Infinipath

2008-08-13 Thread Tom Riddle
Hi, A bit more info wrt the question below. I have run other releases of OpenMPI and they seem to be fine. The reason I need to run the latest is because it supports valgrind fully. openmpi-1.2.4 openmpi-1.3ar18303 TIA, Tom --- On Tue, 8/12/08, Tom Riddle wrote: Hi, I am getting a

[OMPI users] MPI_ERR_TRUNCATE with MPI_Revc without Infinipath

2008-08-12 Thread Tom Riddle
Hi, I am getting a curious error on a simple communications test. I have altered the std mvapich osu_latency test to accept receives from any source and I get the following error [d013.sc.net:15455] *** An error occurred in MPI_Recv [d013.sc.net:15455] *** on communicator MPI_COMM_WORLD [d013.s

Re: [OMPI users] vprotocol pessimist

2008-07-15 Thread Tom Riddle
Jul 15, 2008, at 11:49 AM, Aurélien Bouteiller wrote: > This is a harmless error, related to fault tolerance component. If > you don't need FT, you can safely ignore it. It will disappear soon. > > Aurelien > > > Le 15 juil. 08 à 11:22, Tom Riddle a écrit : > >> Hi

[OMPI users] vprotocol pessimist

2008-07-15 Thread Tom Riddle
Hi, I wonder if anyone can shed some light on what exactly this is referring to? At the start of any mpirun program I get the following mca: base: component_find: unable to open vprotocol pessimist: file not found (ignored) I combed the FAQs and the forum archives but didn't see anything that

Re: [OMPI users] Valgrind Functionality

2008-07-14 Thread Tom Riddle
quot;Rainer Keller" List-Post: users@lists.open-mpi.org Date: Sunday, July 13, 2008, 11:06 AM Hello Tom, There was a bug in the configure.m4 of memchecker/valgrind, but it shouldn't happen for revision 18303. Now it fixed with r18899. Could you please svn update your source, and try ag

Re: [OMPI users] Valgrind Functionality

2008-07-13 Thread Tom Riddle
ity To: rarebit...@yahoo.com, "Open MPI Users" Cc: "Ashley Pittman" List-Post: users@lists.open-mpi.org Date: Sunday, July 13, 2008, 6:16 AM On Jul 13, 2008, at 9:11 AM, Tom Riddle wrote: > Does anyone know if this feature has been incorporated yet? I did a > ./configu

Re: [OMPI users] Valgrind Functionality

2008-07-13 Thread Tom Riddle
7/11/08, Ashley Pittman wrote: From: Ashley Pittman Subject: Re: [OMPI users] Valgrind Functionality To: "Tom Riddle" Cc: "Open MPI Users" List-Post: users@lists.open-mpi.org Date: Friday, July 11, 2008, 8:58 AM On Tue, 2008-07-08 at 18:01 -0700, Tom Riddle wrote: > Tha

Re: [OMPI users] Valgrind Functionality

2008-07-08 Thread Tom Riddle
rebit...@yahoo.com, "Open MPI Users" List-Post: users@lists.open-mpi.org Date: Tuesday, July 8, 2008, 2:05 AM On Mon, 2008-07-07 at 19:09 -0700, Tom Riddle wrote: > > I was attempting to get valgrind working with a simple MPI app > (osu_latency) on OpenMPI. While it appears to repor

[OMPI users] Valgrind Functionality

2008-07-07 Thread Tom Riddle
Hi, I was attempting to get valgrind working with a simple MPI app (osu_latency) on OpenMPI. While it appears to report uninitialized values it fails to report any mallocs or frees that have been conducted. I am using RHEL 5, gcc 4.2.3 and a drop from the repo labeled openmpi-1.3a1r18303. con