[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: ASB at MIT-MC, LEWISR at MIT-MC
- From: Jeffrey P. Golden <JPG at MIT-MC>
- Date: Sat, 21 Nov 81 18:28:00 GMT
- Cc: BUG-LISP at MIT-MC, JPG at MIT-MC
- Original-date: 21 November 1981 13:28-EST
Date: Fri, 21 Nov 81 17:04:20 GMT
Original-Date: 11/21/81 13:04:20 EDT
Date: Fri, 21 Nov 81 02:38:29 GMT
Original-Date: 11/20/81 22:38:29 EDT
Another question, if I may. While something was running (a file was
being loaded), a message ;GLEEP! OUT OF BIT BLOCKS came. However,
the loading concluded and the program proceeded with execution.
What did the message mean, and should I distrust the results of the
I am not really the one to ask about this. The message is printed by Lisp,
and I think it means something like "I am choking so badly that this is just
about all I can tell you about it." I have always found that things
continue quite normally after the message appears, but it is a bit
unnerving. Perhaps JPG can enlighten us both.
I don't really know what it means either. I've tried to get the LISP system
hackers to say something on the subject with no success. E.g. I've never
gotten an answer to the mail I sent below:
JPG@MIT-MC 22 AUG 1978 0350-EDT
To: (BUG LISP) at MIT-MC
CC: JPG at MIT-MC, CHAR at MIT-MC, ELLEN at MIT-MC
It would be nice if something were done about the cute
"gleep! out of bit blocks" message. This message is unintelligible
to us all wrt the state it is trying to convey and its seriousness.
E.g., can a MACSYMA be reasonably continued after the user receives
this message? Can it happen when (STATUS MEMFREE) is not 0?
And exactly what does it mean as far as the functioning of the GC