The configuration looks fine, but from the stack it seems that the
segv is coming from an invalid free in BLCR (which seems odd to me).
Are you able to get a gdb backtrace from a core file generated from
this run? That would provide a bit more detail on where things are
going wrong.
What
Dear All,
I have installed openmpi 1.3.2 in my home directory (
/home/jean/openmpisof/ ) and BLCR in /usr/local/blcr. I have added the
following in the .bashrc file
export PATH=/home/jean/openmpisof/bin/:$PATH
export LD_LIBRARY_PATH=/home/jean/openmpisof/lib/:$LD_LIBRARY_PATH
exp
Dear Jeff and George,
The problem was in our code.
Thanks for your help interpreting the error message.
Best regards,
-Ken Mighell
Based on this info from the error report it appears that the segfault
is generated directly in you application main function. Somehow, you
call a function at address 0x, which doesn't make much sense.
george.
On Feb 25, 2009, at 12:25 , Ken Mighell wrote:
[oblix:21522] [ 0] 2 li
On Feb 25, 2009, at 12:25 PM, Ken Mighell wrote:
We are trying to compile the code with Open MPI on a Mac Pro with 2
quad-core Xeons using gfortran.
The code seem to be running ... for the most part. Unfortunately we
keep getting a segfault
which spits out a variant of the following messa
Dear Open MPI gurus,
We have F90 code which compiles with MPICH on a dual-core PC laptop
using the Intel compiler.
We are trying to compile the code with Open MPI on a Mac Pro with 2
quad-core Xeons using gfortran.
The code seem to be running ... for the most part. Unfortunately we
kee
