unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: stephane chatigny <stephane.chatigny@coractive.com>
Subject: Re: potential memory leak in do loop
Date: Thu, 04 May 2006 10:41:18 -0400	[thread overview]
Message-ID: <e3d3qe$pmp$1@sea.gmane.org> (raw)
In-Reply-To: <4458B106.3030109@coractive.com>

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 <Stephane.Chatigny@coractive.com> 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
>> Guile-user@gnu.org
>> http://lists.gnu.org/mailman/listinfo/guile-user
>>
> 
> 
> 
> 
> _______________________________________________
> Guile-user mailing list
> Guile-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/guile-user
> 



_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


      parent reply	other threads:[~2006-05-04 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02 20:33 potential memory leak in do loop Stephane Chatigny
2006-05-03  1:48 ` Kevin Ryde
2006-05-03 13:32   ` stephane chatigny
2006-05-03 14:09     ` Paul Emsley
2006-05-03 22:47     ` Kevin Ryde
2006-05-04 14:41     ` stephane chatigny [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='e3d3qe$pmp$1@sea.gmane.org' \
    --to=stephane.chatigny@coractive.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).