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

[Mike Miller]

Update of bug #44912 (project octave):

                Severity:              3 - Normal => 5 - Blocker            
                 Summary: Ctrl+C doesn't interrupt and causes SIGABORT at exit
=> Ctrl+C doesn't interrupt and causes SIGABRT at exit

    _______________________________________________________

Follow-up Comment #3:

Rik, do you mean that Ctrl+C used to actually interrupt the pause? I see that
in 3.8.2, I don't remember when that worked or stopped working or what the
status of that has been (bug #37672 is still open).

Dan, SIGINT is the signal sent by Ctrl+C. SIGABRT is typically raised by the
terminate function, which is called in the standard library by the abort
function, std::terminate (which is called for e.g. uncaught exceptions), or by
certain errors in the memory management library (double free, corrupted memory
tables, etc).

Actually I think this is unrelated to the pause function. Ctrl+C is supposed
to interrupt the current line and start a new line (at least it does in the
terminal, used to in the GUI). It doesn't do that anymore. I think something
has broken Octave's normal Ctrl+C handler. Just try hitting Ctrl+C at the
prompt. One Ctrl+C and exiting Octave is ok. Two is ok. Three causes the
SIGABRT.

    _______________________________________________________

Reply to this item at:

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

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