From: Stephen Compall <s11@member.fsf.org>
Cc: guile-devel@gnu.org, Rob Browning <rlb@defaultvalue.org>
Subject: Re: readlink, getcwd memory leaks
Date: 29 Apr 2004 16:14:35 -0500 [thread overview]
Message-ID: <xfy7jvytrk4.fsf@csserver.evansville.edu> (raw)
In-Reply-To: <877jw2h7zz.fsf@zagadka.ping.de>
Marius Vollmer <mvo@zagadka.de> writes:
> Yes, just aborting is maybe a bit inflexible. (I think we have
> discussed this previously.) We could allow the registration of
> handlers (written in C) for out-of-memory and the default handler
> could print a warning, wait a bit, and then retry, backing off
> exponentially. Or something.
All sorts of room for creativity here, I guess, but if that's too much
I think an excellent case would be to exec a configurable program of
your choice, or abort if that fails. In the common case, it is the
Guile-using program itself that has eaten too much memory, so exec
should clear that, and the exec'd program can do whatever complicated
error-handling you like (e.g. pop up a window explaining the problem.
You probably won't be able to load up a GUI library or widgets in the
same program if you ran out of memory :).
--
Stephen Compall or s11 or sirian
The system was down for backups from 5am to 10am last Saturday.
explosion TWA KGB UOP Rule Psix import Kh-11 bce NSA UNSCOM Lon
Horiuchi defense information warfare STARLAN Honduras fraud
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-04-29 21:14 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 [this message]
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=xfy7jvytrk4.fsf@csserver.evansville.edu \
--to=s11@member.fsf.org \
--cc=guile-devel@gnu.org \
--cc=rlb@defaultvalue.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).