Opened 3 days ago
Last modified 3 days ago
#434 new defect
ISOLTS error display doesn't always work reliably
| Reported by: | Eric Swenson | Owned by: | Eric Swenson |
|---|---|---|---|
| Priority: | major | Milestone: | MR12.9 |
| Component: | Tools | Version: | MR12.5 |
| Keywords: | Cc: |
Description
When a page reports an error and then halts at *options?, display_error shows only the errors before it (with a new log, nothing). The error appears only after the next error, the next console message, or the next page. After a report with register or memory dumps, display error with print queues an empty .ilog.
In addition, a display_error while a report is still being written (after a BREAK) leaves a garbage entry in the log (seen as sequence numbers 4307574836 and 15461314157, dated 00/00/00), and the entries written after it are threaded wrongly.
Finally, display error -all does not show the newest entry, and display error N (a count without a limit) shows only Nā 1 entries, so display error 1 shows none.
āhttps://s3.amazonaws.com/eswenson-multics/public/mcrs/MCR10203.pdf