Luca,
you might want to double check the environment :
env | grep ^OMPI
and the per user config
ls $HOME/.openmpi
Cheers,
Gilles
On 2014/12/11 17:40, Luca Fini wrote:
> Many thanks for the replies.
>
> The mismatch in OpeMPI version is my fault: while writing the request
> for help I looked at
Many thanks for the replies.
The mismatch in OpeMPI version is my fault: while writing the request
for help I looked at the name of the directory where OpenMPI was built
(I did not build it myself) and did not notice that the name of the
directory did not reflect the version actually compiled.
I
Hi Luca
Another possibility that comes to mind,
besides mixed versions mentioned by Gilles,
is the OS limits.
Limits may vary according to the user and user privileges.
Large programs tend to require big stacksize (even unlimited),
and typically segfault when the stack is not large enough.
Max
Luca,
your email mentions openmpi 1.6.5
but gdb output points to openmpi 1.8.1.
could the root cause be a mix of versions that does not occur with root
account ?
which openmpi version are you expecting ?
you can run
pmap
when your binary is running and/or under gdb to confirm the openmpi
I've a problem running a well tested MPI based application.
The program has been used for years with no problems. Suddenly the
executable which was run many times with no problems crashed with
SIGSEGV. The very same executable if run with root privileges works
OK. The same happens with other
