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

[Dan Sebald]

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

Well, the octave_qt_link affinity should go back to GUI thread.  Got that
much.

I suspect that the openSUSE configuration/Qt-behavior is showing up again in a
different spot.  That is, the interrupt signal could possibly be queued on
that system.

Let's confirm something on that system.  In the attached patch I've simply
printed out when the GUI terminal window emits its interrupt signal (that's Qt
signal, not OS signal).  Please apply that to a clean repository and report
what you see when hitting Cnrtl-C in the GUI after this change.  This will
tell us whether the issue is Cnrtl-C not being acknowledged by the GUI or if
it's that "interrupt terminal" is not making its way through octave_qt_link.

(file #33788)
    _______________________________________________________

Additional Item Attachment:

File name: print_interrupt_emit-djs2015apr25.diff Size:1 KB


    _______________________________________________________

Reply to this item at:

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

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