On Tue, Feb 21, 2012 at 15:38, John Fettig <john.fettig at gmail.com> wrote:
> Is this likely memory corruption on my side or on the PETSc side, or > something else entirely? I seem unable to reproduce it with an example, > unfortunately. Running it through valgrind may take a week. I don't see a reason why that specific line would naturally end up with an invalid value, so I suspect memory corruption. Make a smaller problem so that valgrind runs fast. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120221/d81defe7/attachment.html>
