Re: [OMPI users] Debug build of v3.0.1 tarball

Ah, yes. That worked. Thanks, Howard. -Adam From: users on behalf of Howard Pritchard Reply-To: Open MPI Users Date: Friday, May 4, 2018 at 1:13 PM To: Open MPI Users Subject: Re:

Re: [OMPI users] Debug build of v3.0.1 tarball

HI Adam, I think you'll have better luck setting the CFLAGS on the configure line. try ./configure CFLAGS="-g -O0" your other configury options. Howard 2018-05-04 12:09 GMT-06:00 Moody, Adam T. : > Hi Howard, > > I do have a make clean after the configure. To be extra

Re: [OMPI users] User-built OpenMPI 3.0.1 segfaults when storing into an atomic 128-bit variable

On Thu, May 3, 2018 at 11:23 PM, Nathan Hjelm wrote: > Not saying we won't change the behavior. Just saying the user can't expect > a particular alignment as there is no guarantee in the standard. In Open > MPI we just don't bother to align the pointer so right now so it

Re: [OMPI users] Debug build of v3.0.1 tarball

Hi Howard, I do have a make clean after the configure. To be extra safe, I’m now also deleting the source directory and untarring for each build to make sure I have a clean starting point. I do get a successful build if I add --enable-debug to configure and then do a simple make that has no

[OMPI users] OpenMPI 3.0.1 - mpirun hangs with 2 hosts

Hello All, I'm trying to set up OpenMPI 3.0.1 on a pair of linux machines, but I'm running into a problem where mpirun hangs when I try to execute a simple command across the two machines: $ mpirun --host b09-30,b09-32 hostname I'd appreciate any assistance with this problem. I'm a new MPI user

Re: [OMPI users] Debug build of v3.0.1 tarball

HI Adam, Sorry didn't notice you did try the --enable-debug flag. That should not have led to the link error building the opal dso. Did you do a make clean after rerunning configure? Howard 2018-05-04 8:22 GMT-06:00 Howard Pritchard : > Hi Adam, > > Did you try using

Re: [OMPI users] Debug build of v3.0.1 tarball

Hi Adam, Did you try using the --enable-debug configure option along with your CFLAGS options? You may want to see if that simplifies your build. In any case, we'll fix the problems you found. Howard 2018-05-03 15:00 GMT-06:00 Moody, Adam T. : > Hello Open MPI team, > > I'm

Re: [OMPI users] Memory leak with pmix_finalize not being called

Ouch - trivial fix. I’m inserting it into PMIx and will provide it to the OMPI team > On May 4, 2018, at 5:20 AM, Saurabh T wrote: > > This is with valgrind 3.0.1 on a Centos 6 system. It appears pmix_finalize > isnt called and this reports leaks from valgrind despite the

[OMPI users] Memory leak with pmix_finalize not being called

This is with valgrind 3.0.1 on a Centos 6 system. It appears pmix_finalize isnt called and this reports leaks from valgrind despite the provided suppression file being used. A cursory check reveals MPI_Finalize calls pmix_rte_finalize which decrements pmix_initialized to 0 before calling

[OMPI users] error building openmpi-master-201805030307-c22c485 on Linux with Sun C

Hi, I've tried to install openmpi-master-201805030307-c22c485 on my "SUSE Linux Enterprise Server 12.3 (x86_64)" with Sun C 5.15 (Oracle Developer Studio 12.6). Unfortunately I still get the following error that I already reported on April 12th. loki

Re: [OMPI users] User-built OpenMPI 3.0.1 segfaults when storing into an atomic 128-bit variable

Not saying we won't change the behavior. Just saying the user can't expect a particular alignment as there is no guarantee in the standard. In Open MPI we just don't bother to align the pointer so right now so it naturally aligns as 64-bit. It isn't about wasting memory. Also remember that by