|
From: Tim R. <ti...@su...> - 2004-04-08 02:12:50
|
In message <066701c41d0b$4c545ee0$b2d0fea9@R22>
"Andreas Raab" <and...@gm...> wrote:
> Which reminds about something totally unrelated but potentially *hugely*
> helpful:
>
> How about if we disable GC in primitives?
From my audit recently to find places that needed looking at for
messing with the 'interrupt check right now' I found very few numbered
prims can trigger a GC. Most of those that could, ought to be rewritten
to fail and let the image work it out. The nastiest case I can remember
is when sending a message and trying to allocate a context; run out of
memory there and there probably isn't much that can be done. Perhaps
automatically send an email to RamChipsRUs.com?
I'd suggest that the VM changes are pretty small but ought to include
the ability to pass back an error value (fortunately I have ancient
code to do that sitting somewhere) so the image knows what the problem
was and does the smart thing.
tim
--
Tim Rowledge, ti...@su..., http://sumeru.stanford.edu/tim
Old programmers never die; they just branch to a new address.
|