OpenMPI version: 1.3.3
Platform: IBM P5
If I configure with just the --prefix option for where to install, and then run
"make all install", I get an "mpi.mod" file in the "lib" directory of the
prefix directory I specified. ALL GOOD!
When I add compiler options to the configure script (e.g. "C
Arunkumar C R wrote:
Hi,
A fortran 90 code having MPI enabled subroutine is written. The
subroutine part is given below,
program abc
.. !usual statements
open(20, file='sum.20', action='write')
open(30, file='sum.40', action='write')
Hi,
A fortran 90 code having MPI enabled subroutine is written. The subroutine
part is given below,
program abc
.. !usual statements
open(20, file='sum.20', action='write')
open(30, file='sum.40', action='write')
n2= 100;nstep=5
Sounds like a bug - the processes should have died via SIGTERM, followed by
SIGKILL. I know we had some problems in that regard, but I'm not sure if the
fixes came into the 1.3.3 release or not.
You might try updating to the 1.4.2rc1 tarball and see if that helps. I
recently fixed a similar iss
"mpirun -version" says "mpirun (Open MPI) 1.3.3"
>>> Ralph Castain 22/04/2010 19:14:18 >>>
Which OMPI version?
On Apr 22, 2010, at 12:04 PM, Jon Hitchcock wrote:
> If a user connects to a cluster using SSH, starts an MPI program which
> contains an infinite loop, and then breaks the SSH connec
Which OMPI version?
On Apr 22, 2010, at 12:04 PM, Jon Hitchcock wrote:
> If a user connects to a cluster using SSH, starts an MPI program which
> contains an infinite loop, and then breaks the SSH connection, the processes
> running the MPI program continue to run on the compute nodes and they
If a user connects to a cluster using SSH, starts an MPI program which contains
an infinite loop, and then breaks the SSH connection, the processes running the
MPI program continue to run on the compute nodes and they have to be killed
manually.
To investigate this, I found that if the user typ
You can run a X-windows server on your local machine and use the GUI for
gdb, or use Eclipse Parallel Tools Platform (http://www.eclipse.org/ptp/)
that has a debugger and turn on X-Forwarding in your Secure Shell client.
-Original Message-
From: users-boun...@open-mpi.org [mailto:users-b
On Thu, 22 Apr 2010 13:11:49 +0200, "=?utf-8?b?0J3QtdC80LDRmtCwINCY0LvQuNGb?=
(Nemanja Ilic)" wrote:
> On the contrary when I debug with "mpirun -np 4 xterm -e gdb
> my_mpi_application" the four debugger windows are started with
> separate thread each, just as it should be. Since I will be using
I don't think the "debugger" option to mpirun will work with gdb - I believe it
is intended to work with parallel debuggers such as Totalview. Looking at the
code, I certainly can't see how gdb would work correctly with it.
There is an mpirun option "-xterm" which will launch the xterm windows
To keep this thread updated:
After I posted to the developers list, the community was able to guide
to a solution to the problem:
http://www.open-mpi.org/community/lists/devel/2010/04/7698.php
To sum up:
The extended communication times while using shared memory communication
of openmpi processe
Hello,
I am using Open MPI 1.4.1
Best regards,
Nemanja Ilic
On Thursday 22 April 2010 16:44:13 you wrote:
> What version of OMPI are you using?
>
> On Apr 22, 2010, at 5:11 AM, Немања Илић (Nemanja Ilic) wrote:
>
> > Hello,
> >
> > I tried to debug with command: "mpirun -debugger gdb -debug
What version of OMPI are you using?
On Apr 22, 2010, at 5:11 AM, Немања Илић (Nemanja Ilic) wrote:
> Hello,
>
> I tried to debug with command: "mpirun -debugger gdb -debug -np 4 my_program"
> Surely, it starts the debugger, but it doesn't start the debugging nor it
> loads any of the my_progra
Hello,
I tried to debug with command: "mpirun -debugger gdb -debug -np 4 my_program"
Surely, it starts the debugger, but it doesn't start the debugging nor it
loads any of the my_program threads into the debugger. If I start debugging
manually ("file my_program", then "run"), I can start only o
14 matches
Mail list logo
