Thanks to all who gave their input. After upgrading to the latest svn version
all is well now. Tom
--- On Sun, 7/13/08, Shiqing Fan wrote:
From: Shiqing Fan
Subject: Re: [OMPI users] Valgrind Functionality
To: rarebit...@yahoo.com, "Open MPI Users"
Cc: "Jeff Squyres" , &
On Jul 14, 2008, at 7:07 AM, Ashley Pittman wrote:
The default in v1.3 is that ptmalloc2 is *not* built into libopen-
pal. This is different than v1.2, where ptmalloc2 *was* included in
libopen-pal unless you specified --disable-memory-manager.
Thank you for clearing that ip Jeff, what is the
On Sun, 2008-07-13 at 09:16 -0400, Jeff Squyres wrote:
> On Jul 13, 2008, at 9:11 AM, Tom Riddle wrote:
>
> > Does anyone know if this feature has been incorporated yet? I did a
> > ./configure --help but do not see the enable-ptmalloc2-internal
> > option.
> >
> > - The ptmalloc2 memory manager
le-debug --enable-memchecker
--with-psm=/usr/include --with-valgrind=/opt/wkspace/valgrind-3.3.0/
I think I'm close, TIA Tom
--- On *Sun, 7/13/08, Jeff Squyres //* wrote:
From: Jeff Squyres
Subject: Re: [OMPI users] Valgrind Functionality
To: rarebit...@yahoo.com, "Op
pace/openmpi-1.3 CC=gcc
CXX=g++ --disable-mpi-f77 --enable-debug --enable-memchecker
--with-psm=/usr/include --with-valgrind=/opt/wkspace/valgrind-3.3.0/
I think I'm close, TIA Tom
--- On Sun, 7/13/08, Jeff Squyres wrote:
From: Jeff Squyres
Subject: Re: [OMPI users] Valgrind Functional
On Jul 13, 2008, at 9:11 AM, Tom Riddle wrote:
Does anyone know if this feature has been incorporated yet? I did a
./configure --help but do not see the enable-ptmalloc2-internal
option.
- The ptmalloc2 memory manager component is now by default built as
a standalone library named libopenm
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
On Tue, 2008-07-08 at 18:01 -0700, Tom Riddle wrote:
> Thanks Ashley, after going through your suggestions we tried our test
> with valgrind 3.3.0 and with glibc-devel-2.5-18.el5_1.1, both exhibit
> the same results. A simple non-MPI test prog however returns expected
> responses, so valgrind itsel
bopen-pal.so is providing its own malloc
replacement
Is there perhaps something I have missed in runtime? I have included the
ompi_info just in case. Thanks in advance. Tom
--- On Tue, 7/8/08, Ashley Pittman wrote:
From: Ashley Pittman
Subject: Re: [OMPI users] Valgrind Functionality
To: ra
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 report uninitialized
> values it fails to report any mallocs or frees that have been
> conducted.
The normal reason for this is
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
11 matches
Mail list logo
