info-mac@uw-beaver (info-mac) (10/28/84)
From: Seth Goldman <seth@UCLA-LOCUS.ARPA>
I have a version of Xlisp 1.2, that behaves very strangely on my Mac.
Depending on the #defines in xlisp.h for NNODES and ANODES, the behavior
changes. Basically I always get some kind of error, occasionally it even
reports itself via an Alert box. Initially I just got a Bomb. I changed
the settings (increased both constants) and then the start of alert box
appeared but then my Mac went dead. I decreased the settings and now
I see an alert box from the xlisp C function LEFT. I decreased the settings
further and type in an expression (fmem). I get an alert box telling
be that xlisp cannot evaluate that exp.
I do have macsbug but unfortunately have not yet received my copy of
'Inside Mac'. NewPtr is used for obtaining more memory. If anyone has
any suggestions for tracking this down or has run into similar problems
please HELP!!! It would appear that the trouble is memory related (128k mac).
Is there some initialization of newly acquired storage that might not be
happening?
Thanks in advance,
Seth Goldman
ARPA: seth@UCLA-LOCUS.ARPA
UUCP: ...!{ihnp4,cepu,trwspp,sdcrdcf,ucbvax}!ucla-cs!seth
USMail: Computer Science Department
A.I. Lab, 3531 Boelter Hall
UCLA
Los Angeles, CA 90024
(213) 825-5199