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

[Dan Sebald]

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

"If it's a peculiarity of my system (virtual machine, openSUSE 13.2, one CPU)
or some system configuration to distinguish between copy and interuption then
maybe the priority can be lowered."

I asked because your system seems like a good one for revealing the
intricacies of threads.  I'm sure there are plenty of people who would
experience the same as part of a release.

The fact you aren't seeing the message indicates that the
QTerminal::interrupt_signal() isn't even being emitted.  So the hypothesis
that the signal is being queued doesn't hold water.  On your system, the
Cntrl-C is not making its way to the terminal.  That, or your system
configuration is routing OS signal differently.  Let me think about this one
for a bit--there are a lot of different "terminal_interrupt" signal/slot
variations to decipher.


    _______________________________________________________

Reply to this item at:

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

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