[bug #51237] Deadlock in Ctrl-C handler on Windows

Follow-up Comment #7, bug #51237 (project make): If you are going to refactor the code which handles SIGINT, then we should return to this issue only after the new code is written. The only Windows-specific aspect of your idea is that the signal handler will still run in a separate thread on

Re: [bug #51237] Deadlock in Ctrl-C handler on Windows

> right before we do something that might "take a long time". Or "right before we do something that could change disk state". On Mon, Jul 10, 2017 at 11:29 AM, Paul D. Smith wrote: > Follow-up Comment #6, bug #51237 (project make): > > It's not the exact same problem

[bug #51237] Deadlock in Ctrl-C handler on Windows

Follow-up Comment #6, bug #51237 (project make): It's not the exact same problem but it's caused by the same flaw in the make code: doing lots of work in a signal handler. What I was hoping to do is change the signal handler to do nothing more than set a flag saying that the fatal signal was

[bug #51434] Document that variables are treated differently in prerequisite lists and recipes

Update of bug #51434 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #1: There is a section of

[bug #51434] Document that variables are treated differently in prerequisite lists and recipes

Additional Item Attachment, bug #51434 (project make): File name: makefile Size:0 KB ___ Reply to this item at: ___ Message sent

[bug #51434] Document that variables are treated differently in prerequisite lists and recipes

URL: Summary: Document that variables are treated differently in prerequisite lists and recipes Project: make Submitted by: None Submitted on: Mon 10 Jul 2017 02:11:04 PM UTC