Hi,
There seem to be three solutions (in best to worst order).
- someone (Ian maybe) needs to rebuild the Unix VM with a VMMaker from within the last two years. Apparently the bug has been fixed for a while.
- pass a fixed memory size to the VM
-memory 200m
or so does the trick.
- patch the existing C source code.
cheers
bruce
On Tue, Mar 03, 2009 at 09:19:13AM +0100, Tudor Girba wrote:
Hi,
I am not sure I got the summary of the discussion related to the problem of deploying a Pharo-based image to seasidehosting. Is there any conclusion?
Cheers, Doru
-- www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
vm-dev@lists.squeakfoundation.org