Re: [OMPI users] Sending string causes memory errors

Something is really weird here ... right after MPI_Recv, if i if (cstr[0] != 'H') cout << "bad first character" << endl; then valgrind complains ! i rewrote the program in C, but if i use subroutines for send(), then MPI_Send fail because of a NULL communicator ... if i manually inline

Re: [OMPI users] Orted path with module manager on cluster

Davide, you can invoke `which mpirun` instead of mpirun, or mpirun --prefix=... an other option is to rebuild OpenMPI with --enable-mpirun-prefix-by-default Cheers, Gilles On 3/4/2016 7:22 AM, Davide Vanzo wrote: Hi all, I have built OpenMPI 1.10.2 with RoCE network support on our test

Re: [OMPI users] Orted path with module manager on cluster

> On 03 Mar 2016, at 23:22 , Davide Vanzo wrote: > I have built OpenMPI 1.10.2 with RoCE network support on our test cluster. On > the cluster we use lmod to manage paths to different versions of softwares. > The problem I have is that I receive the "orted: command

[OMPI users] Pass RoCE flags to srun under SLURM

Hi all, In our cluster the nodes are interconnected with RoCE and I want to set up OpenMPI to run on it via SLURM. I initially compiled OpenMPI 1.10.2 only with IB verbs support and I have no problem making it run over RoCE. Then I have successfully built it with SLURM support as follows:

[OMPI users] Orted path with module manager on cluster

Hi all, I have built OpenMPI 1.10.2 with RoCE network support on our test cluster. On the cluster we use lmod to manage paths to different versions of softwares. The problem I have is that I receive the "orted: command not found" message given that the path to the orted binary is not exported to

Re: [OMPI users] Fw: Open SHMEM Error

Hi Ryan, Unfortunately, the attachments that you shared are too low resolution to make out the code. It sounds like you might be looking at the code in OpenSHMEM 1.1 Section 8.1.6 (attached). Is that right? ~Jim. On Thu, Mar 3, 2016 at 1:15 AM, RYAN RAY wrote: > >

Re: [OMPI users] Sending string causes memory errors

All of those valgrind reports below are from within your code -- not from within Open MPI. All Open MPI can do is pass the contents of your message properly; you can verify that it is being sent and received properly by checking the byte contents of your received array (e.g., assert that the

Re: [OMPI users] Sending string causes memory errors

Hey, Am Donnerstag, 3. März 2016, 17:50:59 CET schrieb Gilles Gouaillardet: > Florian, > > which distro are you running on ? I'm running Arch. > if you are not using stock gcc and valgrind, can you tell which version you > are running ? > last but not least, how did you configure openmpi ?

Re: [OMPI users] Sending string causes memory errors

Am Mittwoch, 2. März 2016, 16:23:02 CET schrieb Jeff Squyres (jsquyres): > There's a bunch of places in OMPI where we don't initialize memory because we > know it doesn't matter (e.g., in padding between unaligned struct members), > but then that memory is accessed when writing the entire struct

Re: [OMPI users] Sending string causes memory errors

Florian, which distro are you running on ? if you are not using stock gcc and valgrind, can you tell which version you are running ? last but not least, how did you configure openmpi ? Cheers, Gilles On Thursday, March 3, 2016, Florian Lindner wrote: > I am still getting

Re: [OMPI users] Sending string causes memory errors

I am still getting errors, even with your script. I will also try to modified build of openmpi that Jeff suggested. Best, Florian % mpicxx -std=c++11 -g -O0 -Wall -Wextra -fno-builtin-strlen mpi_gilles.cpp && mpirun -n 2 ./a.out Stringlength = 64

[OMPI users] Fw: Open SHMEM Error

From: "RYAN RAY" ryan@rediffmail.com Sent: Thu, 03 Mar 2016 12:26:19 +0530 To: "announce " annou...@open-mpi.org, "ryan.ray " ryan@rediffmail.com Subject: Open SHMEM Error On trying a code specified in the manual"OpenSHMEM Specification Draft "asection8.16 example code , we

Re: [OMPI users] Sending string causes memory errors

I was unable to reproduce this in my environment. here is a slightly modified version of your test program. buffers are 64 bytes aligned and the string (including the null terminator) is 64 bytes long, hopefully, strlen will not complain any more. Cheers, Gilles On 3/3/2016 12:51 AM,