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

[John W. Eaton]

Follow-up Comment #18, bug #37672 (project octave):

Michael, what happens if you type Ctrl-C when inv is working on a large
matrix?  For example


x = rand (3000);
inv (x);


Pause for a half second or so before interrupting the inv command because
there is a call to std::copy at the top of that function that must complete
before you get to the code that will react to SIGINT by doing a longjmp.  If
you type Ctrl-C twice while the std::copy is working, you'll get a message
about typing Ctrl-C again to abort Octave.  If you do that before reaching the
code where Octave uses setjmp/longjmp, you'll exit Octave.

What about if you go back to the changeset prior to my latest patches?  Try
"hg up -C c9f622fd7307", then build again and try the test above.  I expect
that Octave will exit when you type Ctrl-C, and that will happen without the
message about typing Ctrl-C again to abort.  So without the patches,
interrupting doesn't work properly.  With them, I'm hoping that it is just
sleep that is affected.


    _______________________________________________________

Reply to this item at:

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

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