From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org
Subject: Re: potential memory leak in do loop
Date: Wed, 03 May 2006 11:48:40 +1000 [thread overview]
Message-ID: <87iron98uf.fsf@zip.com.au> (raw)
In-Reply-To: <390990895AACCE4AA76C5A19872C8ADB233D6C@serveur0.coractive.local> (Stephane Chatigny's message of "Tue, 02 May 2006 16:33:14 -0400")
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 1:48 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 [this message]
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
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=87iron98uf.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-user@gnu.org \
/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).