[petsc-dev] valgrind appears to show memory leak related to PetscViewerBinaryOpen
Jed Brown
jed at 59A2.org
Wed Jun 1 11:27:09 CDT 2011
On Wed, Jun 1, 2011 at 18:24, Matthew Knepley <knepley at gmail.com> wrote:
> You can still use BinaryOpen()
Evidently I'm not capable of reading. I thought Barry was removing
PetscViewerBinaryOpen(). I agree that PetscViewerBinaryCreate() is silly and
should be removed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110601/7e7fe0b3/attachment.html>
More information about the petsc-dev
mailing list