Hi,
I have installed a new open MPI 1.3.4.
But I got more weird errors:
*** glibc detected *** /lustre/nsga2b: malloc(): memory corruption (fast):
0x1cafc450 ***=== Backtrace:
=/lib64/libc.so.6[0x3c50272aeb]/lib64/libc.so.6(__libc_malloc+0x7a)[0x3c5027402a]/usr/lib64/libst
I would recommend you to read OFED (or Mellanox OFED) documentation. It will be
good start point.
Regards,
Pavel (Pasha) Shamis
---
Application Performance Tools Group
Computer Science and Math Division
Oak Ridge National Laboratory
On Mar 14, 2011, at 4:37 PM, Bernardo F Costa wrote:
> O
On Mar 14, 2011, at 4:37 PM, Bernardo F Costa wrote:
> I've tried ibdiagnet and other ofed tools. I also tried to debug the
> network environment with simple jobs to measure bandwidth and latency.
> In most cases, I've seen high peaks of measures who come and go
> without any reason I could catch
You can:
mpirun -np 4 valgrind ./my_application
That is, you run 4 copies of valgrind, each with one instance of
./my_application. Then you'll get valgrind reports for your applications. You
might want to dig into the valgrind command line options to have it dump the
results to files wit
Hi,
I think it is time to see the actual code:) Would it be possible to send us a
part of the code that we can run and test with?
With best regards,
-Belaid.
From: dtustud...@hotmail.com
To: us...@open-mpi.org
List-Post: users@lists.open-mpi.org
Date: Tue, 15 Mar 2011 09:44:35 -0600
Subject: R
This should be the configure info about Open MPI which I am using.
-bash-3.2$ mpic++ -v
Using built-in
specs.
Target:
x86_64-redhat-linux
Configured with:
../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
--enable-shared --enable-threads=posix --enable-checking=relea
I have tried export OMPI_MCA_memory_ptmalloc2_disable=1
It does not work. The same error.
thanks
From: sam...@lanl.gov
To: us...@open-mpi.org
List-Post: users@lists.open-mpi.org
Date: Tue, 15 Mar 2011 09:27:35 -0600
Subject: Re: [OMPI users] OMPI seg fault by a class with weird address.
I -thin
I -think- setting OMPI_MCA_memory_ptmalloc2_disable to 1 will turn off
OMPI's memory wrappers without having to rebuild. Someone please
correct me if I'm wrong :-).
For example (bash-like shell):
export OMPI_MCA_memory_ptmalloc2_disable=1
Hope that helps,
--
Samuel K. Gutierrez
Los Alamos
Thanks,From http://valgrind.org/docs/manual/mc-manual.html#mc-manual.mpiwrap
I find that
"Currently the wrappers are only buildable with mpiccs which are based on GNU
GCC or Intel's C++ Compiler."
The cluster which I am working on is using GNU Open MPI mpic++. i am afraid
that the Valgrind wra
Thanks,
I do not have system administrator authorization. I am afraid that I cannot
rebuild OpenMPI --without-memory-manager.
Are there other ways to get around it ?
For example, use other things to replace "ptmalloc" ?
Any help is really appreciated.
thanks
From: belaid_...@hotmail.com
To:
I'm afraid that this is a bug in the PGI compiler -- Open MPI uses the
offsetof() macro in several places throughout its code base.
This is why we put in the configure test that tells you that your compiler does
not support it -- we got a lot of reports of this issue during the build phase
of O
I am building OFED-1.5.3 on CentOS 5.5 (OFED-1.5.2 build fine) and succeeds
except for openmpi_pgi (OpenMPI 1.4.3). For version 10.9 of the pgi
compilers I get:
configure: WARNING: Your compiler does not support offsetof macro
configure: error: Configure: Cannot continue
error: Bad exit status
You may also want to run your program through a memory-checking debugger such
as valgrind to see if it turns up any other problems.
AFIK, ptmalloc should be fine for use with STL vector allocation.
On Mar 15, 2011, at 4:00 AM, Belaid MOA wrote:
> Hi Jack,
> I may need to see the whole code t
On Monday, March 14, 2011 09:37:54 pm Bernardo F Costa wrote:
> Ok. Native ibverbs/openib is preferable although cannot be used by all
> applications (those who do not have a native ip interface).
Applications (in this context at least) uses the MPI interface. MPI in general
and OpenMPI in pertic
Hi Jack,
I may need to see the whole code to decide but my quick look suggest that
ptmalloc is causing a problem with STL-vector allocation. ptmalloc is the
openMPI internal malloc library. Could you try to build openMPI without memory
management (using --without-memory-manager) and let us kn
Hi,
Because the code is very long, I just show the calling relationship of
functions.
main(){scheduler();
}scheduler(){ ImportIndices();}
ImportIndices(){Index IdxNode ; IdxNode = ReadFile("fileName");}
Index ReadFile(const char* fileinput) { Index TempIndex;.
}
Hi Jack,
1- Where is your main function to see how you called your class?
2- I do not see the implementation of GetPosition, GetName, etc.?
With best regards,
-Belaid.
From: dtustud...@hotmail.com
To: us...@open-mpi.org
List-Post: users@lists.open-mpi.org
Date: Mon, 14 Mar 2011 19:04:12 -0600
17 matches
Mail list logo
