[petsc-users] valgrind

[Mohamad M. Nasr-Azadani]

That "300 bytes" sounds familiar. :-)
I have also seen this before.
According to this,

http://lists.mcs.anl.gov/pipermail/petsc-users/2011-December/011690.html

I think it has something to do with OS and not important.

Best,
Mohamad

Mohamad

On Wed, Feb 15, 2012 at 1:32 AM, Mohammad Mirzadeh <mirzadeh at gmail.com>wrote:

> Hi,
>
> This might just not be important but I'm still curious about it. When I
> run valgrind on this:
>
> int main (int argc, char **argv){
>
>     PetscInitialize(&argc, &argv,(char *)0,help);
>     PetscFinalize();
>
>
>     return 0;
> }
>
> I get,
>
> ==7262== HEAP SUMMARY:
> ==7262==     in use at exit: 300 bytes in 11 blocks
> ==7262==   total heap usage: 203 allocs, 192 frees, 643,759 bytes allocated
> ==7262==
> ==7262== LEAK SUMMARY:
> ==7262==    definitely lost: 60 bytes in 1 blocks
> ==7262==    indirectly lost: 240 bytes in 10 blocks
> ==7262==      possibly lost: 0 bytes in 0 blocks
> ==7262==    still reachable: 0 bytes in 0 blocks
> ==7262==         suppressed: 0 bytes in 0 blocks
> ==7262== Rerun with --leak-check=full to see details of leaked memory
>
>
> Is this normal?
>
> Thanks,
> Mohammad
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20120215/f7d6970a/attachment.htm>