[Top][All Lists]

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

[Octave-bug-tracker] [bug #59100] "__debug_octave__" doesn't work on Win

From: Rik
Subject: [Octave-bug-tracker] [bug #59100] "__debug_octave__" doesn't work on Windows
Date: Sun, 13 Sep 2020 13:45:05 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36

Follow-up Comment #5, bug #59100 (project octave):

So it sounds like the command from comment #2 should be adopted.

The extra bit of text printed in the Octave Command Window, rather than in the
new shell, is annoying but not tragic for an internal function that won't get
executed very often.

I might make a guess that of the two output streams, STDERR and STDOUT,
perhaps system() on Windows is not re-directing STDERR at the same time as

On Linux, 

octave:4> [status, output] = system ("ls NO_SUCH_FILE")
ls: cannot access 'NO_SUCH_FILE': No such file or directory
status = 2
output = 

You can see that STDOUT has been captured in output (but there was nothing to
capture) and that the error message on STDERR went directly to Octave's
command window.  Probably something similar is happening with gdb and when it
was started it sent version information to STDERR.


Reply to this item at:


  Message sent via Savannah

reply via email to

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