OK, it turned out to be a really stupid mistake.
Sorry for spamming and thanks for the help!
Regards,
Aniruddha
On Mon, Sep 28, 2009 at 11:28 AM, Aniruddha Marathe <
marathe.anirud...@gmail.com> wrote:
> Hi Jeff,
>
> Thanks for the pointers. I tried with both CFLAGS=-g3 and --enable-debug
> (se
That may explain it - I never build fortran (thank goodness).
On Sep 28, 2009, at 5:06 PM, Pierre-Olivier Dallaire wrote:
This error only comes out when I try to build the fortran wrappers /
will not fail if only building with gcc/g++
I had to included -all_load in several individual Makefil
This error only comes out when I try to build the fortran wrappers /
will not fail if only building with gcc/g++
I had to included -all_load in several individual Makefile / using the
env variable LIBS with ./configure does not work.
Thanks !
PO
On 2009-09-28, at 6:57 PM, Ralph Castain w
Nope - I've been running on Snow Leopard almost since the day it came
out without problem.
Key was that I had to re-install all my 3rd party software (e.g.,
compilers) from Macports or wherever as none of the stuff I had
installed on Leopard would work properly after the upgrade.
Didn't r
Hi,
when compiling openmpi-1.3.3 with GNU or PGI compilers, the following
occurs :
ibtool: link: gcc-4.2 -O3 -DNDEBUG -m64 -finline-functions -fno-strict-
aliasing -fvisibility=hidden -o orte-iof orte-iof.o ../../../
orte/.libs/libopen-rte.a /Users/podallaire/Downloads/openmpi-1.3.3/
opal/
Hi folks,
I want to use for openmpi communication the additional ethernet interfaces on
node and head node.
its is eth1 on nodes and eth4 on head node.
So how can I configure openmpi?
If I add in config file
btl_base_include=tcp,sm,self.
btl_tcp_if_include=eth1
will it work or not?
And how i
Hi Jeff,
Thanks for the pointers. I tried with both CFLAGS=-g3 and --enable-debug
(separately), however, I am still unable to jump into the MPI source. It
seems I am missing a small step(s) somewhere.
I compiled my MPI application with the new library built with above flags,
ran it and attached g
I've verified that ulimit -l is unlimited everywhere.
After further testing I think the errors are related to OFED not openmpi.
I've uninstalled the OFED that comes with SLES (1.4.0) and installed
OFED 1.4.2 and 1.5-beta and I don't get the errors.
I got the idea to swap out OFED that after re
Thanks for the reply. I looked harder at the command invocation and I think I
stumbled across an answer. My actual mpirun command is invoked from a Python
script using the subprocess module. When you create a subprocess, one of the
options is "shell" and I had that set to False, causing the act
Dear All,
I am trying to integrate DMTCP with openmpi. IF I run a c
application, it works fine. But when I execute the program using mpirun, It
checkpoints application but gives error when restarting the application.
#
[31007] WARNING at connection.cpp:303 in restore; REAS
Thanks.
> From: jsquy...@cisco.com
> To: us...@open-mpi.org
> Date: Mon, 28 Sep 2009 11:49:36 -0400
> Subject: Re: [OMPI users] How to create multi-thread parallel program using
> thread-safe send and recv?
>
> On Sep 28, 2009, at 11:48 AM, guosong wrote:
>
> > Oh, thanks. I found that mpich2/
On Sep 28, 2009, at 11:48 AM, guosong wrote:
Oh, thanks. I found that mpich2/gnu supports MPI_THREAD_MULTIPLE by
default on my server. So if it supports MPI_THREAD_MULTIPLE, does it
mean that I can run the program without segmentation fault (if there
is no other bugs ^_^)
Hypothetically,
Oh, thanks. I found that mpich2/gnu supports MPI_THREAD_MULTIPLE by default on
my server. So if it supports MPI_THREAD_MULTIPLE, does it mean that I can run
the program without segmentation fault (if there is no other bugs ^_^)
> From: jsquy...@cisco.com
> To: us...@open-mpi.org
> Date: Mon, 28
You might want to just configure Open MPI with:
./configure CFLAGS=-g3 ...
That will pass "-g3" to every Makefile in Open MPI.
FWIW: I do variants on this technique and gdb is always able to jump
to the right source location if I "break MPI_Barrier" (for example).
We actually have a "--e
On Sep 27, 2009, at 1:45 PM, guosong wrote:
Hi Loh,
I used MPI_Init_thread(&argc,&argv, MPI_THREAD_MULTIPLE, &provided);
in my program and got provided = 0 which turns out to be the
MPI_THREAD_SINGLE. Does this mean that I can not use
MPI_THREAD_MULTIPLE model?
Correct.
To get Open MPI
Yes I did, forgot to mention that in my last. Most of the example code
I've seen online passes the buffer variable by reference...
I think I've gotten past the segfault at this point, but it looks like
MPI_Isend is never completing. I have an MPI_Test() that sets a flag
immediately following the M
Hello,
I am new to OpenMPI library and I am trying to step through common MPI
communication calls using gdb. I attach gdb to one of the processes
(using the steps mentioned on the OpenMPI Debugging FAQ page) and set
a breakpoint on 'MPI_Barrier' and expect gdb to jump into the
definition of MPI_Ba
You are right. An update fixes the problem.
Sorry.
Thomas
Jeff Squyres wrote:
It's a fairly strange place to get an error --
mca_base_param_finalize() is where we're tidying up command line
parameters.
There was some memory bugs that have been fixed since 21970. Can you
update?
On Sep
18 matches
Mail list logo
