|
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 22:00:29 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0 |
Follow-up Comment #23, bug #53635 (project octave): Yes, that is what's going on. ## run sleep at the bash command prompt $ pgrep sleep 19590 $ grep Sig /proc/19590/status SigQ: 3/63696 SigPnd: 0000000000000000 SigBlk: 0000000000000000 SigIgn: 0000000000000000 SigCgt: 0000000000000000 ## run sleep at the octave command prompt $ pgrep sleep 19855 $ grep Sig /proc/19855/status SigQ: 3/63696 SigPnd: 0000000000000000 SigBlk: 0000000003817007 SigIgn: 0000000000000000 SigCgt: 0000000000000000 The SigBlk field shows that the following signal numbers are being blocked by the sleep process. Left as an exercise for the reader to turn the numbers into signal names. >> (find (fliplr (dec2bin (hex2dec ("0000000003817007"))))).' ans = 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 _______________________________________________________ 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] |