[Top][All Lists]

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

[Octave-bug-tracker] [bug #53635] CTRL-C does not work in all instances

From: Rik
Subject: [Octave-bug-tracker] [bug #53635] CTRL-C does not work in all instances when using Windows GUI
Date: Mon, 16 Apr 2018 12:06:08 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Update of bug #53635 (project octave):

                  Status:            Works For Me => Confirmed              
                 Summary: CTRL-C does not work in Windows GUI => CTRL-C does
not work in all instances when using Windows GUI


Follow-up Comment #10:

Confirmed.  I can break use Ctrl+C to break a while (1) loop, but not to break
the execution of __run_test_suite__.  I have changed the Summary message to
indicate that there is some functionality, but not complete functionality.

Using Windows 4.3.90, and octave-cli.exe I see the following behavior

## Wait a moment for bitfcns.cc or bsxfun.cc to be running their tests.
## Type one Ctrl+C.
## Program seems to halt--there is no activity by octave in the Task
## but control is not returned to the Octave prompt.
## It seems to be waiting for further input.  At this point I can type
## characters and they are echoed to the terminal.  I can also hit <RETURN>.
## All of the input seems to be ignored.
## Type a second Ctrl+C.  The sequence '^C' is echoed to the terminal and
## Octave returns to the prompt.

Interesting things are that the first Ctrl+C is not echoed to the terminal,
but is apparently swallowed and processed by something associated with Octave.
 And it takes a second Ctrl+C to actually exit whatever intermediate state it
is in and return to the prompt.

If I use the GUI the situation is worse.  The first Ctrl+C halts activity by
Octave, as evidenced by zero activity in the Task Manager, but there is no way
to get out of the intermediate state and return to the prompt.  Instead, each
Ctrl+C is merely echoed as '^C'.

If I go back to Windows 4.2.1 and octave-gui.exe then it is roughly similar. 
The first Ctrl+C halts Octave activity and moves it into a terminal state
which accepts input.  The second Ctrl+C is echoed as '^C', but I get a warning
"Press Ctrl+C again to abort".  I can type anything I want, but to get out of
the hung state I eventually have to hit Ctrl+C which does abort Octave.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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