Re: [OMPI users] OMPI users] MPI_ABORT was invoked on rank 0 in communicator compute with errorcode 59

2016-11-16 Thread Gilles Gouaillardet
Hi, With ddt, you can do offline debugging just to get where the program crashes ddt -n 8 --offline a.out ... You might also wanna try the reverse connect feature Cheers, Gilles "Beheshti, Mohammadali" wrote: >Hi Gus, > >Thank you very much for your prompt

Re: [OMPI users] MPI_ABORT was invoked on rank 0 in communicator compute with errorcode 59

2016-11-16 Thread Beheshti, Mohammadali
Hi Gus, Thank you very much for your prompt response. The myjob.sh script is as follows: #!/bin/bash #PBS -N myjob #PBS -l nodes=1:ppn=8 #PBS -l walltime=120:00:00 #PBS -l pvmem=2000MB module load openmpi/2.0.0 cd /cluster/home/t48263uhn/Carp/PlosOneData/ mpirun -np 8 carp.debug.petsc.pt +F

Re: [OMPI users] MPI_ABORT was invoked on rank 0 in communicator compute with errorcode 59

2016-11-15 Thread Gus Correa
Hi Mohammadali "Signal number 11 SEGV", is the Unix/Linux signal for a memory violation (a.k.a. segmentation violation or segmentation fault). This normally happens when the program tries to read or write in a memory area that it did not allocate, already freed, or belongs to another process.