There are some strings which might not get freed, but they are very small. How big are we talking?<br><br> Matt<br><br><div class="gmail_quote">On Sun, Aug 9, 2009 at 5:55 AM, Umut Tabak <span dir="ltr"><<a href="mailto:u.tabak@tudelft.nl">u.tabak@tudelft.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Dear all,<br>
<br>
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).<br>
<br>
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?<br>
<br>
I used "valgrind --leak-check=yes ./ex1"<br>
<br>
Best regards,<br><font color="#888888">
Umut<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener<br>