[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: potential memory leak in do loop
From: |
Paul Emsley |
Subject: |
Re: potential memory leak in do loop |
Date: |
Wed, 3 May 2006 15:09:17 +0100 |
User-agent: |
Mutt/1.5.8i |
I suspect you need valgrind. valgrind rocks.
You will need the standard guile suppressions.
Paul.
On Wed, May 03, 2006 at 09:32:54AM -0400, stephane chatigny wrote:
> Thanks Kevin,
>
> Does a Unix command like "pmap PID" could help me to determine if there
> is a memory leak in the process?
>
> I have run the program for 24hrs and the memory usage seems to be
> constant at ~28-30Mb. It usually takes 36hrs to generate the bug, I will
> wait and see if the memory usage remains constant.
>
> regards
> Stef
>
>
> Kevin Ryde a ?crit :
> >Stephane Chatigny <address@hidden> writes:
> >>(although I have not tracked the memory usage yet).
> >
> >You'll probably have to use one of the various malloc debugging
> >packages to find who has allocated the memory that's never freed, to
> >see who's supposed to be responsible for that.