Thanks, I've gotten to the point of building and running branch/1.3. However when I attempt to run my simple osu_latency test I get the following runtime error now, which I hadn't before on a repo pull of trunk/openmpi-1.3a1r18303
opal_memchecker_base_select failed
--> Returned value -13 instead od OPAL_SUCCESS
I checked the ompi_info and see the following memchecker
MCA memchecker: parameter "memchecker" (current value: <none>
Default selection set of components for the memchecker framework
so that looks ok, here is my configure
$ ../configure --prefix=/opt/wkspace/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 <jsquyres@cisco.com> wrote:
From: Jeff Squyres <jsquyres@cisco.com>
Subject: Re: [OMPI users] Valgrind Functionality
To: rarebitusa@yahoo.com, "Open MPI Users" <users@open-mpi.org>
Cc: "Ashley Pittman" <apittman@concurrent-thinking.com>
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
> ./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 libopenmpi-malloc. Users wanting to
> use leave_pinned with ptmalloc2 will now need to link the
library
> into their application explicitly. All other users will use the
> libc-provided allocator instead of Open MPI's ptmalloc2. This
> change
> may be overriden with the configure option enable-ptmalloc2-internal
> --> Expected: 1.3
This is on the trunk/v1.3 branch, yes.
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.
--
Jeff Squyres
Cisco Systems |