[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: (BUG LISPM) at MIT-AI
- From: rms@MIT-AI (Sent by ___016@MIT-AI)
- Date: Sat ,16 Sep 79 13:30:26 EDT
How about making a sequence break history table
which would record certain information about each sequence break
except for those which are "trivial"
as defined by something such as that the scheduler stack group is running.
This ought to make it much easier to debug strange occurrences,
especially if there is an escape command to copy the history table
into a saved place for leisurely examination.