[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: Rik
Subject: [Octave-bug-tracker] [bug #52556] Octave stops writing to console
Date: Tue, 5 Dec 2017 13:57:22 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

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

If I just open Octave and issue an freport I get:

octave:1> freport

  number  mode  arch       name
  ------  ----  ----       ----
     0     r    ieee-le    stdin
     1     w    ieee-le    stdout
     2     w    ieee-le    stderr

The difference between my report and yours are the two fids python-in and
python-out.  Presumably these are pipes used for communication with python
that were created by the symbolic package.  It may be that python or the
symbolic package is messing around with stdout and stderr and where they are
connected (they should be connected to the console at all times).

What happens if you don't load the symbolic package, or other external code,
and use Octave?  For example, try running the built-in test suite to stress
the interpreter with


After running the test suite, can you execute commands correctly and have the
output show up in the console window?

It is also possible that the console code for Microsoft Windows isn't very


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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