[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: BR at MIT-MC
- From: JPG at MIT-MC (Jeffrey P. Golden)
- Date: Fri, 23 Jun 78 22:17:00 GMT
- Cc: (BUG LISP) at MIT-MC, JPG at MIT-MC
- Original-date: 23 JUN 1978 1817-EDT
Date: Thu, 23 Jun 78 00:53:06 GMT
Original-Date: 06/22/78 20:53:06 EDT
USING (CONTROL)] TO FIND OUT THE RUN TIME VERY OFTEN RESULTS
IN THE DESTRUCTION OF THE CALCULATION. TYPICAL MESSAGES
ARE LOST USER INTERRUPT OR (LATELY) SOME LONG MESSAGE INVOVLVING
FILE SPECS BEING LOST. VERY OFTEN MEANS ONCE OR TWICE A SESSION....
FROM THE USER POINT OF VIEW RATHER OFTEN.
I agree that this problem is serious. I have not heard of this occurring
for quite some time now previous to your message. Unfortunately this is
a LISP bug with LISP's interrupt scheme that is particularly difficult to
track down. Perhaps with HIC's help we can devise a breakpoint scheme or
something that would make it easier to debug this when it occurs.