id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
434	ISOLTS error display doesn't always work reliably	Eric Swenson	Eric Swenson	"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."	defect	new	major	MR12.9	Tools	MR12.5