[Octave-bug-tracker] [bug #37623] MinGW: Crash on incorrect syntax

[Michael Goffioul]

Follow-up Comment #14, bug #37623 (project octave):

All these results are consistent and point in the direction of failure to
detect stdin/stdout as TTY.

When interactive and line-editing flags are not set, an error will make octave
to exit, and octave will not use readline internally. The readline REPL is
used differently by the FLTK and Qt backends:
- FLTK runs the GUI event loop synchronously with octave, events are processed
during idle time in the readline REPL; no readline == no GUI events being
processed
- Qt runs the GUI event loop in a separate thread, but uses the readline REPL
when it needs to run some piece of code synchronously with octave, for
instance to run callbacks, e.g. when closing a window; no readline => no
callbacks being processed and windows do not close

So the issue is that gnulib::isatty() fails on stdin and/or stdout on Windows
8. I've attached a small test program. Would you be able to compile and run it
on Windows 8? If you installed the MinGW version of octave, you should have
everything you need to compile that problem (as it comes bundled with a
compiler). To compile with gcc, use the command:

gcc -O2 -o test-tty.exe test-tty.c

To compile with Visual Studio, use this instead:

cl -O2 -MD -Fetest-tty.exe test-tty.c

For reference, the test program on a WinXP 32 bits gives:

isatty (stdin): 64
IsConsoleHandle (stdin): 1
isatty (stdout): 64
IsConsoleHandle (stdout): 1

The "IsConsoleHandle()" macro is a gnulib trick that is based on a strong
assumption [1], which may not be valid anymore on Windows 8.

[1] http://lists.gnu.org/archive/html/bug-gnulib/2009-08/msg00065.html

    _______________________________________________________

Reply to this item at:

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

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