Ted,
fwiw, the 'master' branch has the behavior you expect.
meanwhile, you can simple edit your 'dum.sh' script and replace
/home/buildadina/src/aborttest02/aborttest02.exe
with
exec /home/buildadina/src/aborttest02/aborttest02.exe
Cheers,
Gilles
On 6/15/2017 3:01 AM, Ted Sussman wrot
The "error *** glibc detected *** $(PROGRAM): double free or corruption" is
ubiquitous and rarely has anything to do with MPI.
As Gilles said, use a debugger to figure out why your application is
corrupting the heap.
Jeff
On Wed, Jun 14, 2017 at 3:31 AM, ashwin .D wrote:
> Hello,
>
Hi,
at first, i suggest you decide which Open MPI version you want to use.
the most up to date versions are 2.0.3 and 2.1.1
then please provide all the info Jeff previously requested.
ideally, you would write a simple and standalone program that exhibits
the issue, so we can reproduce and inv
Hello,
I found a thread with Intel MPI(although I am using gfortran
4.8.5 and OpenMPI 2.1.1) -
https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/564266
but the error the OP gets is the same as mine
*** glibc detected *** ./a.out: double free or c
