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

[Philip Nienhuis]

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

(In response to Mike's request at bug #40156)

In 3.7.6+ GUI (MXE-cross-built, on WinXP), trying to interrupt 'system ("sleep
50")' doesn't work. I get after Ctrl-C twice separated three secs apart:

octave-cli.exe:1> system ("sleep 50")
Press Ctrl-C again to abort


...and the next (3rd) Ctrl-C kills Octave with an error about 
"The instruction at '0x67777e70' referencing memory at '0x00000000'. The
memory could not be read
Click OK to terminate the program"

I tend to suspect this is due to Octave calling an external program; either
Octave doesn't correctly transfer the interrupt to sleep(), or sleep() itself
doesn't want to be interrupted (improbable I think), or Octave doesn't
correctly pick up sleep()'s return. I'd go for the first because sleep() goes
on and on.... it apparently never gets the signal.

*However*... in 3.7.6+ CLI, interrupting 'system ("sleep 50")' gives (after
Ctrl-C within 3 secs):

octave-cli.exe:1> system ("sleep 50")
ans =  258

octave-cli.exe:1>


and promptly returns to the prompt (no pun intended) after Ctrl-C so in the
CLI it works OK (I can only vouch for my own box, of course).
FYI, on 3.6.4 the return value is 0 rather than 258.

Internal stuff (i.e., scripts, Octave commands) CAN be interrupted - already
in Octave-3.6.4. I never noted a regression. I've been busy lately with
processing (big) spreadsheets; time-consuming stuff like complicated regexps
on MB size strings can be aborted, w/o effects for stability etc.


    _______________________________________________________

Reply to this item at:

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

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