Re: [OMPI devel] OMPI devel] OpenMPI 2.x: bug: violent break at beginning with (sequential) runs...

2016-09-30 Thread Jeremy McCaslin
Hi, Can I please be removed from this list? Thanks, Jeremy On Thu, Sep 15, 2016 at 8:44 AM, r...@open-mpi.org wrote: > I don’t think a collision was the issue here. We were taking the > mpirun-generated jobid and passing it thru the hash, thus creating an > incorrect and invalid value. What I’

Re: [OMPI devel] Memory trace using valgrind in OpenMPI

2016-09-30 Thread Gilles Gouaillardet
Did you run ? valgrind --trace-malloc=yes a.out if yes, then malloc() and free() are traced. hex numbers are the results of malloc or arguments of free, so these are pointers to the heap (e.g. data). these are not pointers to instructions and hence cannot be converted to source code/line number.

Re: [OMPI devel] Memory trace using valgrind in OpenMPI

2016-09-30 Thread Emani, Murali
Attached is a sample of memory tracing using valgrind for malloc/free. — Murali From: devel mailto:devel-boun...@lists.open-mpi.org>> on behalf of Gilles Gouaillardet mailto:gilles.gouaillar...@gmail.com>> Reply-To: Open MPI Developers mailto:devel@lists.open-mpi.org>> Date: Friday, September

Re: [OMPI devel] Memory trace using valgrind in OpenMPI

2016-09-30 Thread Gilles Gouaillardet
Can you provide a sample of the valgrind output ? I do not believe there should be any hex there Cheers, Gilles On Friday, September 30, 2016, Emani, Murali wrote: > Thanks Gilles,I’ve tried using these options but still cannot get the > trace in the source code. > > — > Murali > > > From: dev

Re: [OMPI devel] Memory trace using valgrind in OpenMPI

2016-09-30 Thread Emani, Murali
Thanks Gilles,I’ve tried using these options but still cannot get the trace in the source code. — Murali From: devel mailto:devel-boun...@lists.open-mpi.org>> on behalf of Gilles Gouaillardet mailto:gilles.gouaillar...@gmail.com>> Reply-To: Open MPI Developers mailto:devel@lists.open-mpi.or