On 03/17/2011 03:31 PM, vaibhav dutt wrote:
Hi,
Thanks for your reply. I tried to execute first a process by using
mpirun -machinefile hostfile.txt --slot-list 0:1 -np 1
but it gives the same as error as mentioned previously.
Then, I created a rankfile with contents"
rank 0=t1.tools.xxx
On 03/17/2011 03:31 PM, vaibhav dutt wrote:
Hi,
Thanks for your reply. I tried to execute first a process by using
mpirun -machinefile hostfile.txt --slot-list 0:1 -np 1
but it gives the same as error as mentioned previously.
Then, I created a rankfile with contents"
rank 0=t1.tools.xxx
Getting deeper into valgrind- and debugger-identified errors is somewhat
outside the scope of this mailing list -- we're really here to talk about Open
MPI-related things.
I suggest you read the valgrind documentation and/or google around for other
memory debugging resources.
Good luck.
On
On 18 Mar 2011, at 06:07, Jack Bryan wrote:
> Hi,
>
> I am running a C++ program with OMPI.
> I got error:
>
> *** glibc detected *** /nsga2b: free(): invalid next size (fast):
> 0x01817a90 ***
This error indicates that when glibc tried to free some memory the internal
data
thanks,
I forgot to set up storage capacity for some a vector before using [] operator
on it.
thanks
> Subject: Re: [OMPI users] OMPI seg fault by a class with weird address.
> From: jsquy...@cisco.com
> Date: Wed, 16 Mar 2011 20:20:20 -0400
> CC: us...@open-mpi.org
> To:
Hi,
I am running a C++ program with OMPI.I got error:
*** glibc detected *** /nsga2b: free(): invalid next size (fast):
0x01817a90 ***
I used GDB:
=== Backtrace: =Program received signal SIGABRT,
Aborted.0x0038b8830265 in raise () from /lib64/libc.so.6(gdb) bt#0
> Date: Thu, 17 Mar 2011 23:40:31 +0100
> From: dominik.goedd...@math.tu-dortmund.de
> To: us...@open-mpi.org
> Subject: Re: [OMPI users] Potential bug in creating MPI_GROUP_EMPTY handling
>
> glad we could help and the two hours of stripping things down were
> effectively not wasted. Also
