Closed
Description
The current implementation of the printer device (dprinter) flushes output inside printer_step4k, that is, only every 4096 simulator steps. Possibly, this was done to improve simulation speed, but as a result the print output is not visible when single stepping using the gdb interface. This is not a problem in the msim interface, because it uses the same output as the machine and flushes during command prompts.
(I can do the change, the reason for the ticket is I'm not sure there aren't other reasons for the delayed flush.)
Metadata
Metadata
Assignees
Labels
No labels