memory leak from valgrind on ex1

Matthew Knepley knepley at
Sun Aug 9 08:52:54 CDT 2009

There are some strings which might not get freed, but they are very small.
How big are we talking?


On Sun, Aug 9, 2009 at 5:55 AM, Umut Tabak <u.tabak at> wrote:

> Dear all,
> I was trying to locate my memory-leaking problems due to a class I wrote in
> combination with Petsc, during these checks I used valgrind in the very
> basic modes, but there is a point I could not understand about Petsc
> programs. I used the example which is the in the "getting started" section
> of the manual(${PETSC_DIR}/src/ksp/ksp/examples/tutorials/ex1.c).
> A linear system solution. Using valgrind on this problem reported some
> "definitely lost" parts. I could not understand this error. Can someone help
> me on understanding this point, I am not a pro, but want to become a user of
> Petsc by trying to understand the main parts of the library?
> I used  "valgrind --leak-check=yes ./ex1"
> Best regards,
> Umut

What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the petsc-users mailing list