From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: readlink, getcwd memory leaks
Date: Sun, 25 Apr 2004 08:51:25 +1000 [thread overview]
Message-ID: <87wu45gfbm.fsf@zip.com.au> (raw)
In-Reply-To: <87r7uddnnk.fsf@zagadka.ping.de> (Marius Vollmer's message of "Sun, 25 Apr 2004 00:19:43 +0200")
Marius Vollmer <mvo@zagadka.de> writes:
>
> (There still will be a memory leak when scm_mem2string throws, but that
> is very unlikely...)
I was thinking about that after Dirk changed scm_gethostbyname. Looks
like a lot of potential places like that, and no fun to try to tighten
them up :-(.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-04-24 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 20:12 readlink, getcwd memory leaks Kevin Ryde
2004-04-24 22:19 ` Marius Vollmer
2004-04-24 22:51 ` Kevin Ryde [this message]
2004-04-24 23:42 ` Marius Vollmer
2004-04-25 8:16 ` Dirk Herrmann
2004-04-25 18:38 ` Rob Browning
2004-04-26 19:08 ` Marius Vollmer
2004-04-29 21:14 ` Stephen Compall
2004-04-28 0:24 ` Kevin Ryde
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=87wu45gfbm.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).