From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: readlink, getcwd memory leaks
Date: Wed, 28 Apr 2004 10:24:18 +1000 [thread overview]
Message-ID: <87n04x7xvx.fsf@zip.com.au> (raw)
In-Reply-To: <87pt9xc59k.fsf@zagadka.ping.de> (Marius Vollmer's message of "Sun, 25 Apr 2004 01:42:15 +0200")
Actually, one easy approach for some of these mallocing things might
be to hold the blocks in an SCM, rather than registering a frame
handler thingie. If there's an error throw then the gc will pick up
the pieces.
scm_make_string or whatever does the trick for malloc, is there some
sort of scm_resize_string hiding? Just for internal use (at least
initially).
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-04-28 0:24 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
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 [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=87n04x7xvx.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).