:11 PM, users-requ...@open-mpi.org wrote:
--
Message: 6
Date: Fri, 25 Apr 2008 14:10:57 -0600
From: Brian Barrett
Subject: Re: [OMPI users] Memory question and possible bug in 64bit
addressing under Leopard!
To: Open MPI Users
Message-ID:
Content-Type: text
Brian,
Thanks, and my apologies.
This is an issue once known to me on an old CRAY/SGI, but lost in the
mists of time (>10 years). Stack size increase did the trick. Of
course putting everything on the heap via new and malloc would work
for arrays, but that creates such an inelegant looking c
9 standard but not in C++.
Martin
-Original Message-
From: users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org] On Behalf
Of Brian Barrett
Sent: April 25, 2008 16:11
To: Open MPI Users
Subject: Re: [OMPI users] Memory question and possible bug in 64bit addressing
under Leopar
On Apr 25, 2008, at 4:10 PM, Brian Barrett wrote:
On Apr 25, 2008, at 2:06 PM, Gregory John Orris wrote:
produces a core dump on a machine with 12Gb of RAM.
and the error message
mpiexec noticed that job rank 0 with PID 75545 on node mymachine.com
exited on signal 4 (Illegal instruction).
On Apr 25, 2008, at 2:06 PM, Gregory John Orris wrote:
produces a core dump on a machine with 12Gb of RAM.
and the error message
mpiexec noticed that job rank 0 with PID 75545 on node mymachine.com
exited on signal 4 (Illegal instruction).
However, substituting in
float *X = new float[n];
fo
OK folks,
Whilst testing cases of ratcheting up memory usage under Mac OSX
Leopard I ran into a peculiar problem of segmentation faults that just
should not be happening. I whittled down the code to find where the
error took place and well, for this simple code...
#include
#include
int
