|
| From: | Mike Miller |
| Subject: | [Octave-bug-tracker] [bug #53635] CTRL-C does not work in all instances when using Windows GUI |
| Date: | Wed, 18 Apr 2018 21:48:54 -0400 (EDT) |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0 |
Follow-up Comment #22, bug #53635 (project octave):
Is Octave's new default signal blocking setup inherited by child processes? I
think that might be the case. I am only able to kill a 'sleep' or a 'yes'
process started from Octave by sending them a SIGKILL, the normal SIGINT and
SIGTERM signals seem to be ignored.
It's possible the only reason emacs works is because emacs is complex enough
that it's setting up its own signal handling and masking and unmasking the
signals it wants to receive.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?53635>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |