Re: potential memory leak in do loop

[stephane chatigny]

Thanks Kevin and Paul,

I am little bit rusty with Linux.  I have not used it since my graduate 
studies ten years ago. I was not aware of the "top" command. I will 
monitor the process with it. Right now the memory usage seems fairly 
constant at 30Mb.

If I need to use some kind of debuging package, I guess that I will need 
at least to recompile "mpb" with the proper debugging flag. That will 
help to see if the problems comes from mpb.

Do I have also to recompile "Guile" with the debuging flags on?


thanks
Stef





stephane chatigny a écrit :
> 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.
> >
> >
> > _______________________________________________
> > Guile-user mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/guile-user
>
>
>
>
> _______________________________________________
> Guile-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/guile-user