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
&
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
crashed
afteridentifying problems in your program, there's a good chancethat fixing
those problems will prevent Valgrind aborting orcrashing, especially if it
happened in m_mallocfree.c.
> Subject: Re: [OMPI users] OMPI seg fault by a class with weird address.
> From: jsquy...@cisco.com
> D
out and see what valgrind tells you.
> >
> >
> >
> > On Mar 15, 2011, at 11:25 AM, Jack Bryan wrote:
> >
> > > Thanks,
> > >
> > > From http://valgrind.org/docs/manual/mc-manual.html#mc-manual.mpiwrap
> > >
> > > I
][n332:82320] *** End of
error message ***=>> PBS: job killed: walltime 117 exceeded limit 90mpirun:
killing job...
> Subject: Re: [OMPI users] OMPI seg fault by a class with weird address.
> From: jsquy...@cisco.com
> Date: Tue, 15 Mar 2011 12:50:41 -0400
> CC: us...@open-mpi
r which I am working on is using GNU Open MPI mpic++. i am afraid
> that the Valgrind wrapper can work here.
>
> I do not have system administrator authorization.
>
> Are there other mem-checkers (open source) that can do this ?
>
> thanks
>
> Jack
>
> &
: Re: [OMPI users] OMPI seg fault by a class with weird address.
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
-redhat-linux
Thread model: posix
gcc version 4.1.2
20080704 (Red Hat 4.1.2-50)
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 -think
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
tmalloc" ?
Any help is really appreciated.
thanks
From: belaid_...@hotmail.com
To: dtustud...@hotmail.com; us...@open-mpi.org
Subject: RE: [OMPI users] OMPI seg fault by a class with weird
address.
Date: Tue, 15 Mar 2011 08:00:56 +
Hi Jack,
I may need to see the whole code to deci
at the Valgrind wrapper can work here.
I do not have system administrator authorization.
Are there other mem-checkers (open source) that can do this ?
thanks
Jack
> Subject: Re: [OMPI users] OMPI seg fault by a class with weird address.
> From: jsquy...@cisco.com
> Date: Tue, 15 Mar
ail.com
To: dtustud...@hotmail.com; us...@open-mpi.org
Subject: RE: [OMPI users] OMPI seg fault by a class with weird address.
List-Post: users@lists.open-mpi.org
Date: Tue, 15 Mar 2011 08:00:56 +
Hi Jack,
I may need to see the whole code to decide but my quick look suggest that
p
e. ptmalloc is not needed if you are not using an RDMA interconnect.
>
> With best regards,
> -Belaid.
>
> From: dtustud...@hotmail.com
> To: belaid_...@hotmail.com; us...@open-mpi.org
> Subject: RE: [OMPI users] OMPI seg fault by a class with weird address.
> Dat
know the outcome.
ptmalloc is not needed if you are not using an RDMA interconnect.
With best regards,
-Belaid.
From: dtustud...@hotmail.com
To: belaid_...@hotmail.com; us...@open-mpi.org
Subject: RE: [OMPI users] OMPI seg fault by a class with weird address.
List-Post: users@lists.open-mpi.org
cpp:8686 Index TempIndex;(gdb) bt#0 ReadFile
(fileinput=0xd6bbb3 "prepdata/idx_ud.csv") at src/index.cpp:86#1
0x00471cc9 in ImportIndices () at src/index.cpp:116#2
0x0043bba6 in main (argc=, argv=) at src/nsga2/main-seq.cpp:32
-
-0600
Subject: [OMPI users] OMPI seg fault by a class with weird address.
Hi,
I got a run-time error of a Open MPI C++ program.
The following output is from gdb:
--Program
received signal SIGSEGV, Segmentation fault
Hi,
I got a run-time error of a Open MPI C++ program.
The following output is from gdb:
--Program
received signal SIGSEGV, Segmentation fault.0x2b3b0b81 in
opal_memory_ptmalloc2_int_malloc () from
/opt/openmpi-
17 matches
Mail list logo