[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SI
From: |
Dan Sebald |
Subject: |
[Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit |
Date: |
Sun, 26 Apr 2015 17:20:15 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 |
Follow-up Comment #25, bug #44912 (project octave):
OK, thanks. Neither cntrl-C nor copy is working for you. That is likely not
a thread issue on your system. Perhaps we should apply changeset
https://savannah.gnu.org/bugs/download.php?file_id=33780
and open a new bug report so that discussion for the behavior you are seeing
is separate from the this bug-report thread.
I do see a couple lines of investigation for this changeset
http://hg.savannah.gnu.org/hgweb/octave/rev/bd1369a2a651
but I'll let T cogitate about those.
First, might it be that this conditional construct
if (text.isEmpty () && ! extra_interrupt)
emit interrupt_signal ();
else
QApplication::clipboard()->setText(text);
should be more along the lines
if (text.isEmpty ())
if (! extra_interrupt)
emit interrupt_signal ();
else
QApplication::clipboard()->setText(text);
Also, I don't see in that changeset anywhere that the new variable
_extra_interrupt is directly initialized anywhere. That doesn't meant it
isn't initialized indirectly, but the place that _extra_interrupt is set is
via QTerminal::notice_settings() and that is a slot. Perhaps that slot is
called when the QTerminal is constructed, but like I said I'll let someone
else first look more closely at that.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?44912>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, (continued)
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Rik, 2015/04/25
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Rik, 2015/04/25
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Dan Sebald, 2015/04/25
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Guillaume, 2015/04/25
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, John W. Eaton, 2015/04/25
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Dan Sebald, 2015/04/25
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Dan Sebald, 2015/04/25
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Torsten, 2015/04/26
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Guillaume, 2015/04/26
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, John W. Eaton, 2015/04/26
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit,
Dan Sebald <=
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Guillaume, 2015/04/26
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Rik, 2015/04/27
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Torsten, 2015/04/27
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Guillaume, 2015/04/27
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Torsten, 2015/04/27
- [Octave-bug-tracker] [bug #44912] Ctrl+C doesn't interrupt and causes SIGABRT at exit, Dan Sebald, 2015/04/27