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

[Dan Sebald]

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

OK, it must be that all signals are not handled properly.  Hitting Cntrl-C
three times without the program responding issues an abort to the program,
which also isn't handled as explained by the exit message.

In the changeset

http://hg.savannah.gnu.org/hgweb/octave/rev/89d843d6de14

is a lot of code hunks not even touched by the example, so it must be this one
change:

+
+  // Move this link object affinity to the same thread as the
+  // interpreter to ensure signals/slots to the GUI are queued.
+  moveToThread (main_thread);

and if I recall correctly, the queuing of signals wasn't the problem
ultimately.  Let's move that back and see what happens with the attached
changeset.

If this works, we'll ask that this bug

https://savannah.gnu.org/bugs/?44751

be checked again, but I don't think it should be a problem.

Thanks for bisecting.

(file #33780)
    _______________________________________________________

Additional Item Attachment:

File name: octave-octave_qt_think_thread_affinity-djs2015apr24.patch Size:0 KB


    _______________________________________________________

Reply to this item at:

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

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