[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #52556] Octave stops writing to console

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #52556] Octave stops writing to console
Date: Mon, 10 Dec 2018 13:25:57 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48

Follow-up Comment #13, bug #52556 (project octave):

(Philip here)
I vaguely remember something about garbled characters in the console but those
memories need a bit refreshing.

Maybe related, but I do regularly see that there's no more output to the GUI
terminal after what looks like some buffer overflow that seems to wipe code
for displaying text in the terminal.
E.g., read a big text file with:

more off;
fid = fopen (<some filename of a fairly big file>);
txt = fread (fid, Inf, "*char")
## note absent semicolon at end of last line

... and then very often there's no more output shown at all.

more on

then and trying typing commands indicates that the pager line is displayed but
with background color (i.e., invisible).
I couldn't yet establish a robust test case so I didn't report it yet, but it
could be relevant here (just guessing).


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]