We are using clisp that originates from Karlsruhe on a vanilla win95 box.
Here the puzzle:
- Our clisp interpreter starts nicely and, as I understand it, consumes
about 2MB of space (even when one requests upto 64MB)
- The documentation describes that it increments space as needed at run
time
- Things run fine when small (a few KB) data files are loaded in
- The whole thing crashes rudely when a 900KB file is loaded in:
<<<<<<<
*** - handle_fault error2 ! address = 0x1800000C not in
[0x19E90000,0x19E90074)!
SIGSEGV cannot be cured. Fault address = 0x1800000C.
>>>>>>>
Possibilities:
A- Clisp is intrinsically sick
B- Clisp is OK but runs into swap space limitations
C- Clisp cant increment dynamically space under win95
D- ??
Please send suggestions to:
···@netcom.com
···@techone.com
TX a lot!
----
Dennis de Champeaux OntoOO Inc email: ···@netcom.com & ···@acm.org
Page: 408 581 2185 Mesg & Fax: 408 559 7264 Res: 408 559 9413
Address: 14519 Bercaw Ln, San Jose, CA 95124, USA
Your objectives can be our objects & your objects can be our objectives(TM)
(Adv) DdC "Object-Oriented Development Process and Metrics"
Prentice Hall, ISBN 0-13-099755-2