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

[Georg Wiora]

URL:
  <http://savannah.gnu.org/bugs/?52556>

                 Summary: Octave stops writing to console
                 Project: GNU Octave
            Submitted by: gwiora
            Submitted on: Thu 30 Nov 2017 09:58:19 AM CET
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: gwiora
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.1
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

I have frequently problems getting console output in the octave-GUI console
window. I can not give a minimal example to produce this effect. Currently I
see this effect when working with the symbolic package but I got this effect
in other not well defined situations too.

I tried to analyze what happens: After console output was lost I switched on
the diary and called freport. In my case it showed the following state in the
diary file only.

> freport

  number  mode  arch       name
  ------  ----  ----       ----
     0     r    ieee-le    stdin
     1     w    ieee-le    stdout
     2     w    ieee-le    stderr
     3     r    ieee-le    python-in
     4     w    ieee-le    python-out


For me this points in the direction of the connection between octave core's
console output and GUI console. I guess this sometimes breaks.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?52556>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/