These are the bt's of 2 cores ..
gdb hello core.14653
#0 0x00300bc0cbc0 in ?? ()
#1 0x2b09d0fb in ?? ()
#2 0x7fff6a782920 in ?? ()
#3 0x2ae3d348 in ?? ()
#4 0x7fff6a7827b0 in ?? ()
#5 0x003806e6bcb4 in ?? ()
#6 0x in ?? ()
gdb hello core.146
I cannot interpret the raw core files since they are specific your
system and setup. Can you run it through gdb and get a backtrace? "gdb
hello core.1234" then use the 'bt' command from inside gdb.
That will help me start to focus in on the problem.
Cheers,
Josh
On Oct 8, 2008, at 10:22 PM,
I have configured with the additional flags(--enable-ft-thread
--enable-mpi-threads) but there is no change in behaviour, it still
gives seg fault.
open mpi version:
Open MPI: 1.3a1r19685
blcr version:
version 0.7.3
The core file is attached.
hello.c is sample mpi program whose core is dumped is
The installation looks ok, though I'm not sure what is causing the
segfault of the restarted process. Two things to try. First can you
send me a backtrace from the core file that is generated from the
segmentation fault. That will provide insight into what is causing it.
Second you may try
Hi all,
This is the procedure i have followed to install openmpi. Is there
some installation or environment setting problem in here?
an openmpi program with 4 process is run across 2 dual-core intel
machines, with 2 processes running on each of the machine.
ompi-checkpoint is successful but ompi-
Hi all,
I had gone through some previous ompi-restart issues but i couldn't
find anything similar to this problem.
I have installed blcr, and configured open-mpi 'openmpi-1.3a1r19645'
i) If the sample mpi program say ( np 4 on single machine that is
without any hostfile )is ran and I try to chec
