Compile with -traceback and -check all if using Intel. Otherwise find the right compiler options to check array bounds accesses and to dump a stack trace. Then compile debug and run that way. Assuming it fails, you probably will get good info on the source of the problem. If it doesn't fail then the compiler has a bug (not as rare as you might think).
You need to look at the application output. Not the output from mpirun. Ed Sent via the Samsung Galaxy S™ III, an AT&T 4G LTE smartphone -------- Original message -------- From: Ralph Castain <r...@open-mpi.org> Date: To: Open MPI Users <us...@open-mpi.org> Subject: Re: [OMPI users] Open MPI exited on signal 11 (Segmentation fault). Trying to run a script that uses Open MPI Well, it's telling you that your program segfaulted - so I'd start with that, perhaps looking for any core it might have dropped. On Jul 4, 2013, at 8:36 PM, Rick White <raw...@gmail.com> wrote: Hello, I have this error: mpiexec noticed that process rank 1 with PID 16087 on node server exited on signal 11 (Segmentation fault) Wondering how to fix it? Cheers and many thanks Rick -- Richard Allen White III M.S. PhD Candidate - Suttle Lab Department of Microbiology & Immunology The University of British Columbia Vancouver, BC, Canada cell. 604-440-5150 http://www.ocgy.ubc.ca/~suttle/ _______________________________________________ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users
