[Octave-bug-tracker] [bug #37672] CTRL+C interrupt processing causes segfaults

[Mike Miller]

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

I haven't seen this problem, because apparently the following line causes this
to start working (explicitly shown here to cause a change in the way the
terminal interrupts are handled):


./run-octave -qfH --no-gui
>> pause (10);
^C ## no effect, pause runs to completion
>> 
>> [a,b] = system ("true");
>> pause (10);
^C
>> ## interrupt works now


My ~/.octaverc actually calls gnuplot, but the program that is called in
system() doesn't seem to matter, what matters is that the output is captured
with nargout == 2. This is enough to apparently restore terminal interrupt
handling enough so that this works.

May have something to do with the octave-gui executable and doing something to
the terminal attributes when it starts up.

    _______________________________________________________

Reply to this item at:

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

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