I somewhat arbitrarily came across this bug:
https://github.com/open-mpi/ompi/issues/299
I have an application which does `fun' things to a subprocess' memory
layout, and I worry that mucking with symbols (particularly malloc and
mmap) will break some assumptions I make. Is there a way to disa
.7.5, but they'll get there.
I'll defer to Ralph for the rest of the discussion about info keys.
On Dec 13, 2013, at 9:16 AM, tom fogal wrote:
Hi Ralph, thanks for your help!
Ralph Castain writes:
It would have to be done via MPI_Info arguments, and we never had a
request to do
small patches
attached. One gets rid of warnings about unused functions in generated
lexing code. I believe the second fixes resource leaks on error paths.
However, it turned out none of my user-level code hit that function at
all, so I haven't been able to test it. Take from it what you will.
Hi all,
I'm developing on Open MPI 1.4.5-ubuntu2 on Ubuntu 13.10 (so, Ubuntu's
packaged Open MPI) at the moment.
I'd like to pass environment variables to processes started via
MPI_Comm_spawn. Unfortunately, the MPI 3.0 standard (at least) does
not seem to specify a way to do this; thus I have b
Our project is fork / exec'ing in some cases to provide a service for
some of the processes within our MPI job. Open MPI spews big warnings
to the terminal about this. It explains how to disable the message,
but I'd really like it to not pop up regardless.
The child process does not perform any
mentioned
that the issue goes away if he installs librdmacm-devel), it sounds
like librdmacm-devel is a "build-dep", but the openmpi-devel package
needs it as a "dep".
Anyway, I'll leave it up to you to forward the error/conclusion to
whomever your upstream is. Thanks
ch paths (or maybe at all). Is it possible
that `mpic++ -show' includes/adds "-lrdmacm" even when OpenMPI is not
itself using the library?
Thanks,
-tom
> On Tue, Dec 15, 2009 at 8:46 PM, tom fogal wrote:
>
> > Simon Su writes:
> > > I am getting this erro
eds.
> Would that help?
Tremendously, thank you.
-tom
> On Tue, Jun 9, 2009 at 11:40 AM, tom fogal wrote:
>
> > jody writes:
> > > I made a suppression file for the irrelevant memory leaks of ompi: I
> > > make no claim that it catches all possible ones, but
>
> > On Jun 9, 2009, at 2:31 AM, Ashley Pittman wrote:
> >
> >> On Mon, 2009-06-08 at 23:41 -0600, tom fogal wrote:
> >> > George Bosilca writes:
> >> > > There is a whole page on valgrind web page about this topic. Please
> >> > &
d then send only that much of the
> > buffer. Thus, the uninitialized portion is ignored.
> >
> > I don't know of a way to tell valgrind to ignore it, I'm afraid -
> > perhaps a valgrind guru can be of help. :-/
> >
> > Ralph
> >
> >
> &
Hi all,
I've configured a source build of OpenMPI 1.3.2 with valgrind enabled
[1], and I'm seeing a lot of errors with writev() when I run this under
valgrind. For example, with the following `hello, world' program:
#include
#include
int main(int argc, char *argv[]) {
MPI_Init(&argc
11 matches
Mail list logo
