[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #51237] Deadlock in Ctrl-C handler on Windows
|
From: |
Michael Builov |
|
Subject: |
[bug #51237] Deadlock in Ctrl-C handler on Windows |
|
Date: |
Thu, 15 Jun 2017 05:20:41 -0400 (EDT) |
|
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0 |
Follow-up Comment #2, bug #51237 (project make):
>> ...Would you be willing to assign copyright for your changes to the FSF...
Yes, I will, no problem.
>> ...signaling the event you added will not interrupt that wait...
New event is not supposed to interrupt Main thread waiting for sub-processes.
Event is waited only by Ctrl+C handler thread and is signaled by Main thread
just before it goes to infinite sleep.
By default, CTRL+C signal is passed to all console processes that are attached
to the console.
So, normally, all console sub-processes spawned by make are stopped by
CTRL+C.
Only processes without console (GUI apps) or that have explicitly detached
console (via FreeConsole) are not stopped by Ctrl+C.
But that kind of processes are unlikely run by make, killing them is
questionable.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51237>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/