[Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABORT at exit

[Dan Sebald]

Follow-up Comment #2, bug #44912 (project octave):

I noticed this not working the other day, but I recalled (maybe incorrectly)
something about a Preferences setting controling the Cntrl-C behavior (is it
"interrupt", or is it "copy").  I couldn't find such a setting so paid no more
thought to it.

In any case, that warning message is issued in main.in.c:


          while (true)
            {
              WAITPID (gui_pid, &status, 0);

              if (caught_signal > 0)
                {
                  int sig = caught_signal;

                  caught_signal = -1;

                  kill (gui_pid, sig);
                }
              else if (WIFEXITED (status))
                {
                  retval = WEXITSTATUS (status);
                  break;
                }
              else if (WIFSIGNALLED (status))
                {
                  std::cerr << "octave exited with signal "
                            << WTERMSIG (status) << std::endl;
                  break;
                }
            }


My guess would be simply that the control-C interrupt signal is being ignored
and, consequently, the command interpreter not interrupted.  Thus, when the
main routine checks the PID status of the gui, i.e., WAITPID (gui_pid,
&status, 0);, at the time of exit it finds that there was an unhandled signal.
 If I type SIG on my system:

https://savannah.gnu.org/bugs/?38305#comment29

signal 6 is ABRT.  I'm pretty sure that what cntrl-C triggers.

Somewhere along the way, the GUI lost the ability to respond to the ABRT
signal.

    _______________________________________________________

Reply to this item at:

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

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