From: Paul Emsley <emsley@ysbl.york.ac.uk>
Subject: Re: potential memory leak in do loop
Date: Wed, 3 May 2006 15:09:17 +0100 [thread overview]
Message-ID: <20060503140917.GC4611@ysbl.york.ac.uk> (raw)
In-Reply-To: <4458B106.3030109@coractive.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1036 bytes --]
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 <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
next prev parent reply other threads:[~2006-05-03 14:09 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 [this message]
2006-05-03 22:47 ` Kevin Ryde
2006-05-04 14:41 ` stephane chatigny
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=20060503140917.GC4611@ysbl.york.ac.uk \
--to=emsley@ysbl.york.ac.uk \
/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).