[Octave-bug-tracker] [bug #37672] GUI doesn't react to CTRL+C

[Mike Miller]

Update of bug #37672 (project octave):

                  Status:          Ready For Test => Confirmed              

    _______________________________________________________

Follow-up Comment #14:

Setting status back to confirmed since we have a couple of cases here that are
not responding to user interrupt correctly.

Here's another one:


octave:1> system ("sleep 5")
^Cans = 2


In the command line, any child process receives the SIGINT, in this case the
command exits immediately and the exit status is non-zero.

Same with the 'F' command in the less pager, which runs to the end of the
input and waits for a user interrupt. If it cannot be interrupted, it never
returns and Octave has to be killed. See bug #37468 (assigning as a duplicate
of this bug now).

In the GUI both of these examples just hang, the child process does not
receive the SIGINT.

    _______________________________________________________

Reply to this item at:

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

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