[petsc-users] tons of valgrind errors with simply PetscInitialize and PetscFinalize?

[Jed Brown]

David Liu <daveliu at mit.edu> writes:

> Hi, I'm running a very simple code, consisting of just PetscFinalize and
> PetscInitialize and nothing else.
>
> I'm running it with valgrind using the command
> "valgrind ./run"
>
> I also tried (as the petsc homepage suggests)
> ${PETSC_DIR}/bin/petscmpiexec -valgrind -n 1 ./run -malloc off
>
> For both cases, I get tons of error messages like
> "Conditional jump or move depends on uninitialised value(s)"
> "Use of uninitialised value of size 8"
> "Invalid read of size 8"
> "Address 0xc15a998 is 40 bytes inside a block of size 47 alloc'd"

You have to send the *exact and complete* output, not snippets.  Are you
using Open MPI?  Chances are this is in the stack somewhere because we
regularly test PETSc itself using valgrind.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20140122/ad722aad/attachment.pgp>