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

[Dan Sebald]

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

OK, clipboard copy noted... yes, that shouldn't affect the issue here.

Furthermore, Guillaume tested the repository as far back as early February
(https://savannah.gnu.org/bugs/?44912#comment26) and found Cntrl-C is not
working then already.  I think that openSUSE system is really testing thread
behavior somehow.  What's interesting is that the Cntrl-C problem is primarily
in the GUI Qt realm.  The question is how to determine why the
terminal_interrupt() slot isn't being called/signaled.  We know graphical
objects and most of the GUI is run in the main thread of the process. 
However, where is the keyboard Qt code executing from?  Same thread?  I'll
look that over sometime in the next couple days and see if there are some
things Guillaume can test on openSUSE to determine what is happening.

    _______________________________________________________

Reply to this item at:

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

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