Hi Oscar
As Ralph suggested, the problem is indeed a memory access violation,
a typical violation of array bounds.
Not really an MPI or OpenMPI problem to be addressed
by this mailing list.
Your ran2 function has a memory violation bug.
It declares dimension ir(1000),
but, the algorithm generate
Sounds like you're freeing memory that does not belong to you. Or you have
some kind of memory corruption somehow.
On Apr 17, 2014, at 2:01 PM, Oscar Mojica wrote:
> Hello guys
>
> I used the command
>
> ulimit -s unlimited
>
> and got
>
> stack size (kbytes, -s) unlimited
Hello guys
I used the command
ulimit -s unlimited
and got
stack size (kbytes, -s) unlimited
but when I ran the program got the same error. So I used the gdb debugger, I
compiled using
mpif90 -g -o mpivfsa_versao2.f exe
I ran the program and then I ran gdb with both the executable
Unfortunately, each execution of mpirun has no knowledge of where the procs
have been placed and bound by another execution of mpirun. So what is
happening is that the procs of the two jobs are being bound to the same
cores, thus causing contention.
If you truly want to run two jobs at the same ti
Hi all,
I've compiled OMPI 1.8 on a x64 linux cluster using the PGI compilers v14.1
(I've tried it with PGI v11.10 and get the same result). I'm able to compile
with the resulting mpicc/mpifort/etc. When running the codes, everything seems
to be working fine when there's only one job running on
