Did you run with a memory checking debugger like Valgrind?
Sent from my phone. No type good.
On Mar 15, 2011, at 8:30 PM, "Jack Bryan" wrote:
> Hi,
>
> I have installed a new open MPI 1.3.4.
>
> But I got more weird errors:
>
> *** glibc detected *** /lustre/nsga2b: malloc(): memory corr
Greetings!!!
I am trying to build openmpi-1.3.4 and openmpi-1.4.3 on Windows 7 (64-bit
OS), but getting some difficuty...
My build environment:
OS : Windows 7 (64-bit)
C/C++ compiler : Visual Studio 2008 and Visual Studio 2010
Fortran compiler: Intel "ifort"
Approach
Hi Hiral,
The 1.4 series doesn't have Fortran support on Windows. You need to use
1.5.
Damien
On 16/03/2011 4:47 AM, hi wrote:
Greetings!!!
I am trying to build openmpi-1.3.4 and openmpi-1.4.3 on Windows 7
(64-bit OS), but getting some difficuty...
My build environment:
OS : Windows 7
Hi Hiral,
1.3.4 is quite old, please use the latest version. As Damien noted, the
full fortran support is in 1.5 series, it's only experimental in 1.4
series. And there is only F77 bingdings on Windows, no F90 bindings.
Another choice is to use the released binary installers to avoid
compilin
Hi Shiquing / Damien,
Thanks for the quick reply.
> it's only experimental in 1.4 series. And there is only F77 bingdings on
Windows, no F90 bindings.
Can you please provide steps to build 1.4.3 with experimental f77 bindings
on Windows?
BTW: Do you have any idea on: when next stable release wit
Hi Hiral,
> it's only experimental in 1.4 series. And there is only F77
bingdings on Windows, no F90 bindings.
Can you please provide steps to build 1.4.3 with experimental f77
bindings on Windows?
Well, I highly recommend to use 1.5 series, but I can also take a look
and probably provide you
Hiral,
To add to Shiqing's comments, 1.5 has been running great for me on
Windows for over 6 months since it was in beta. You should give it a try.
Damien
On 16/03/2011 8:34 AM, Shiqing Fan wrote:
Hi Hiral,
> it's only experimental in 1.4 series. And there is only F77
bingdings on Windows
I have a user whos code when ran on ethernet performs fine. When ran on verbs
based IB the code deadlocks in an MPI_AllReduce() call.
We are using openmpi/1.4.3 with the intel compilers.
I poked at the running code with padb and I get the following:
051525354...
Although I do not think that Valgrind supports mpic++, I have tried to run it.
This is what I got,
thanks==18729==
Memcheck, a memory error detector==18729== Copyright (C) 2002-2009, and GNU
GPL'd, by Julian Seward et al.==18729== Usi
Dears folks,
Recently, I was upgrading openmpi from 1.4.2 to 1.4.3, now, I can see
that system cpu usage is too high, for example, namd application has 40%
system cpu and HPL benchmark has 80%! of system cpu usage, in the
previous version, the system cpu usage was never more than 5%.
I wa
Make sure you have the latest version of valgrind.
But it definitely does highlight what could be real problems if you read down
far enough in the output.
> ==18729== Invalid write of size 8
> ==18729==at 0x443BEF: initPopPara(population*,
> std::vector std::allocator >&, initParaType&, int
This could be related to https://svn.open-mpi.org/trac/ompi/ticket/2714 and/or
https://svn.open-mpi.org/trac/ompi/ticket/2722.
There isn't much info in the ticket, but we've been talking about it a bunch
offline. IBM and Mellanox have had reports of the error, but haven't been able
to reproduc
CPU time is fairly meaningless.
Is the overall run time of your application significantly different?
On Mar 16, 2011, at 1:45 PM, Claudio Baeza Retamal wrote:
> Dears folks,
>
> Recently, I was upgrading openmpi from 1.4.2 to 1.4.3, now, I can see that
> system cpu usage is too high, for exa
13 matches
Mail list logo
