$ ompi_info | grep -i debug Configure command line: '--prefix=/home/jsquyres/bogus' '--with-usnic' '--with-libfabric=/home/jsquyres/libfabric-current/install' '--enable-mpirun-prefix-by-default' '--enable-debug' '--enable-mem-debug' '--enable-mem-profile' '--disable-mpi-fortran' '--enable-debug' '--enable-mem-debug' '--enable-picky' Internal debug support: yes Memory debugging support: yes C/R Enabled Debugging: no
That should tell you whether you have debug support or not. > On Jul 11, 2018, at 5:25 PM, Noam Bernstein <noam.bernst...@nrl.navy.mil> > wrote: > >> On Jul 11, 2018, at 11:29 AM, Jeff Squyres (jsquyres) via users >> <users@lists.open-mpi.org> wrote: >>>> >>> >>> After more extensive testing it’s clear that it still happens with 2.1.3, >>> but much less frequently. I’m going to try to get more detailed info with >>> version 3.1.1, where it’s easier to reproduce. > > objdump —debugging produces output consistent with no debugging symbols in > the library so files: > tin 1061 : objdump --debugging > /usr/local/openmpi/3.1.1_debug/x86_64/ib/intel/11.1.080/lib/libmpi.so.40 > > /usr/local/openmpi/3.1.1_debug/x86_64/ib/intel/11.1.080/lib/libmpi.so.40: > file format elf64-x86-64 > > > Noam -- Jeff Squyres jsquy...@cisco.com _______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
