FWIW, the only memory manager we have will only be active on Linux, not OS X.
As Ralph says, we no longer have access to such systems to test with -- you might try rolling back to an earlier version of Open MPI that we know did work on Snow Leopard...? You might also try compiling with --enable-static --disable-shared; that might give you a better stack trace (sometimes when a segv occurs in an OMPI plugin, you don't get reliable stack traces). You might also try running through valgrind to see if anything obvious pops out...? On Apr 10, 2013, at 10:10 AM, Ralph Castain <r...@open-mpi.org> wrote: > Hi Gus > > I feel your pain - that's a pretty old system! > > I obviously don't have any way to test it, but try configuring OMPI > --without-memory-manager and see if that helps. > > > On Apr 9, 2013, at 9:33 PM, Gustavo Correa <g...@ldeo.columbia.edu> wrote: > >> Dear Open MPI Pros >> >> Somehow I am stuck offsite and I have to test/develop an MPI program on a >> super duper >> 2006 vintage Mac PowerBookPro with Mac OS X 10.6.8 (Snow Leopard). >> This is a 32-bit machine with dual core Intel Core Duo processors and 2GB >> RAM. >> >> Well, my under-development program using FFTW3 and OMPI 1.6.4 runs >> flawlessly on Linux, but I am offsite and I have to use the darn Mac, >> where I get all sorts of weird errors out of the blue, which are >> very likely to be associated to the Mac OS X underlying memory management >> system. >> >> I say so because the OMPI test programs (connectivity_c.c, etc), which do NOT >> allocate memory (other than the MPI internal buffers, if so), run correctly, >> but once I >> start using dynamic memory arrays, boomer, it breaks (but only on the Mac). >> >> I enclose below one of the error messages, FYI. >> [It shows up as a segfault, but the array and buffer boundaries are correct, >> and the program runs perfectly on Linux. RAM is OK also, my batch of test >> data is small. No automatic arrays on the code either.] >> >> I read the OMPI FAQ on runtime issues, and a couple of them mention trouble >> for OMPI >> with the Mac OS X memory management scheme. However, those FAQ are quite >> old, >> refer to OMPI 1.2 and 1.3 series only, recommend linking to an OMPI library >> that seems to have been phased out (-lopenmpi-malloc), and didn't shed the >> light >> I was hoping for. >> >> So, before I give this effort up as not viable, here are a few questions: >> >> Are there specific recommendations on how to build OMPI 1.6.4 on Mac OS X >> 1.6.8? >> Are there any additional linker flags that should be used to build OMPI >> applications under OS X? >> Are there any runtime options that should be added to mpiexec to make OMPI >> programs >> that allocate memory dynamically to run correctly on Mac OS X? >> >> Thank you, >> Gus Correa >> ************************ Error message >> ************************************************************* >> [1,0]<stderr>:[Macintosh-72:36578] *** Process received signal *** >> [1,0]<stderr>:[Macintosh-72:36578] Signal: Segmentation fault (11) >> [1,0]<stderr>:[Macintosh-72:36578] Signal code: Address not mapped (1) >> [1,0]<stderr>:[Macintosh-72:36578] Failing at address: 0x6648000 >> [1,0]<stderr>:[Macintosh-72:36578] [ 0] 2 libSystem.B.dylib >> 0x9728c05b _sigtramp + 43 >> [1,0]<stderr>:[Macintosh-72:36578] [ 1] 3 ??? >> 0xffffffff 0x0 + 4294967295 >> [1,0]<stderr>:[Macintosh-72:36578] [ 2] 4 wcdp3d >> 0x0001be49 main + 1864 >> [1,0]<stderr>:[Macintosh-72:36578] [ 3] 5 wcdp3d >> 0x000027ad start + 53 >> [1,0]<stderr>:[Macintosh-72:36578] [ 4] 6 ??? >> 0x00000002 0x0 + 2 >> [1,0]<stderr>:[Macintosh-72:36578] *** End of error message *** >> >> >> _______________________________________________ >> users mailing list >> us...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/users > > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
