unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Lynn Winebarger <owinebar@free-expression.org>
Cc: hanwen@cs.uu.nl, guile-devel@gnu.org
Subject: Re: port initialization?
Date: Sat, 10 Aug 2002 09:12:37 -0500	[thread overview]
Message-ID: <02081009123711.05101@locke.free-expression.org> (raw)
In-Reply-To: <877kiy7s8v.fsf@zagadka.ping.de>

On Saturday 10 August 2002 08:33, Marius Vollmer wrote:
> Lynn Winebarger <owinebar@free-expression.org> writes:
> 
> >   If you're running out of memory, you might be in a deeply
> > recursed procedure that hasn't set any global variables,
> > so when it aborts, many megabytes become garbage.  It's
> > not that unusual.
> 
> Yes, but for throwing the error, we will also need some fresh storage,
> I think.  We could arrange things so that aborting will always work,
> but I'm afraid that would be quite tricky, and for little gain on a
> Unix-like OS.  Might be different for embedded systems.

    Will it take more than some small fixed amount?  It's not a sin to 
reserve a few words to deal with such situations.
     A related question is, what happens when you're low on memory
and send an interrupt signal?  Will the debugger (be able to) come
up?  Alternatively, to invoke the debugger when it bombs out by keeping
some memory in reserve (make a switch for it).  I suspect guaranteeing that
would require not only a decent call/cc implementation but a way to give the
garbage collector a new chunk of memory to handle (sort of call/cc on the 
gc).  Probably too much work, but it might help writers of such silly algorithms
see the error of their ways.

Lynn


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-08-10 14:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-04 14:42 port initialization? Han-Wen
2002-08-08 17:33 ` Marius Vollmer
2002-08-08 19:35   ` Han-Wen Nienhuys
2002-08-08 20:31     ` Marius Vollmer
2002-08-08 20:54       ` Han-Wen Nienhuys
2002-08-08 21:14         ` Marius Vollmer
2002-08-08 23:17           ` Han-Wen Nienhuys
2002-08-10 13:30             ` Marius Vollmer
2002-08-16 22:06               ` Han-Wen Nienhuys
2002-08-17  0:21                 ` Marius Vollmer
2002-08-08 23:20           ` Lynn Winebarger
2002-08-09  8:06             ` Han-Wen Nienhuys
2002-08-10 13:33             ` Marius Vollmer
2002-08-10 14:12               ` Lynn Winebarger [this message]
2002-08-11 15:57                 ` Marius Vollmer
2002-08-08 19:37   ` Han-Wen Nienhuys
2002-08-08 20:32     ` Marius Vollmer
2002-08-08 23:07       ` Han-Wen Nienhuys
2002-08-10 13:09         ` Marius Vollmer
2002-08-16 22:06           ` Han-Wen Nienhuys

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=02081009123711.05101@locke.free-expression.org \
    --to=owinebar@free-expression.org \
    --cc=guile-devel@gnu.org \
    --cc=hanwen@cs.uu.nl \
    /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).