> This is memory overwriting. Use valgrind to find it.
Valgrind gives it a clean bill of health:
==30174== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 153 from 1)
==30174== malloc/free: in use at exit: 0 bytes in 0 blocks.
==30174== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==30174== For counts of detected errors, rerun with: -v
==30174== All heap blocks were freed -- no leaks are possible.
What am I actually even looking for? Myself overwriting stuff or a PETSc bug?
I do not quite understand how PETSc even could manage to overwrite unrelated
vectors. Or do you suspect I overwrite the vector structure at somepoint and
that confuses PETSc later on?
Cheers,
Juha
--
-----------------------------------------------
| Juha J?ykk?, juhaj at iki.fi |
| http://www.maths.leeds.ac.uk/~juhaj |
-----------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20111217/2fa4c580/attachment.pgp>
