[petsc-users] valgrind

[Kuhlemann, Verena]

So, the first real error that I get is

 Invalid write of size 4
==24909==    at 0x9B3B9F: Moc_ComputePartitionParams__ (kwayrefine.c:215)
==24909==    by 0x9A1D28: Moc_Global_Partition__ (kmetis.c:231)
==24909==    by 0x9A1D00: Moc_Global_Partition__ (kmetis.c:228)
==24909==    by 0x9A1D00: Moc_Global_Partition__ (kmetis.c:228)
==24909==    by 0x9A1D00: Moc_Global_Partition__ (kmetis.c:228)
==24909==    by 0x9A1D00: Moc_Global_Partition__ (kmetis.c:228)
==24909==    by 0x9A1619: ParMETIS_V3_PartKway (kmetis.c:137)
==24909==    by 0x557AC8: MatPartitioningApply_Parmetis (pmetis.c:97)
==24909==    by 0x554058: MatPartitioningApply (partition.c:236)
==24909==    by 0x404DE2: main (runtests.c:99)

Any ideas why?

I will try to use --download-mpich for valgrind debugging./

Thanks,

Verena
________________________________________
From: petsc-users-bounces at mcs.anl.gov [petsc-users-bounces at mcs.anl.gov] on behalf of Satish Balay [balay at mcs.anl.gov]
Sent: Tuesday, August 02, 2011 1:35 PM
To: PETSc users list
Subject: Re: [petsc-users] valgrind

Also suggest using --download-mpich - for valgrind debugging. [it gives
you a valgrind clean mpich]


Satish

On Tue, 2 Aug 2011, Matthew Knepley wrote:

> On Tue, Aug 2, 2011 at 5:06 PM, Kuhlemann, Verena <vkuhlem at emory.edu> wrote:
>
> >  Hi,
> >
> >  I am trying to find an error in my program with valgrind.
> > The first message that I get is the following:
> >
>
> No, MPICH is doing something that valgrind does not understand with memory.
> You can usually
> ignore anything that goes back into MPI.
>
>    Matt
>
>
> >  Syscall param write(buf) points to uninitialised byte(s)
> > ==22395== Syscall param write(buf) points to uninitialised byte(s)
> > ==22393==    at 0x73D92C0: __write_nocancel (in /lib64/libc-2.5.so)
> > ==22393==    by 0x7A76283: ibv_cmd_modify_qp (in
> > /usr/lib64/libibverbs.so.1.0.0)
> > ==22393==    by 0x88B742A: ??? (in /usr/lib64/libmlx4-rdmav2.so)
> > ==22393==    by 0x7A7A363: ibv_modify_qp (in
> > /usr/lib64/libibverbs.so.1.0.0)
> > ==22393==    by 0x67A3DDF: MPID_VIA_Init (viainit.c:1014)
> > ==22393==    by 0x67826BB: MPID_Init (mpid_init.c:66)
> > ==22393==    by 0x677438E: MPIR_Init (initutil.c:279)
> > ==22393==    by 0x432732: PetscInitialize (pinit.c:561)
> > ==22395==    at 0x73D92C0: __write_nocancel (in /lib64/libc-2.5.so)
> > ==22395==    by 0x7A76283: ibv_cmd_modify_qp (in
> > /usr/lib64/libibverbs.so.1.0.0)
> > ==22395==    by 0x88B742A: ??? (in /usr/lib64/libmlx4-rdmav2.so)
> > ==22395==    by 0x7A7A363: ibv_modify_qp (in
> > /usr/lib64/libibverbs.so.1.0.0)
> > ==22395==    by 0x67A3DDF: MPID_VIA_Init (viainit.c:1014)
> > ==22395==    by 0x67826BB: MPID_Init (mpid_init.c:66)
> > ==22395==    by 0x677438E: MPIR_Init (initutil.c:279)
> > ==22395==    by 0x432732: PetscInitialize (pinit.c:561)
> > ==22395==    by 0x4046FC: main (runtests.c:48)
> > ==22395==  Address 0x7feffef78 is on thread 1's stack
> >
> >  I am not sure what this is suppose to tell me. Is the something wrong
> > with my PetscInitialize?
> >
> >  Thanks for the help,
> >
> >  Verena
> >
> >
> > ------------------------------
> >
> > This e-mail message (including any attachments) is for the sole use of
> > the intended recipient(s) and may contain confidential and privileged
> > information. If the reader of this message is not the intended
> > recipient, you are hereby notified that any dissemination, distribution
> > or copying of this message (including any attachments) is strictly
> > prohibited.
> >
> > If you have received this message in error, please contact
> > the sender by reply e-mail message and destroy all copies of the
> > original message (including attachments).
> >
>
>
>
>