[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses

2013-11-29 Thread Eli Zaretskii
Follow-up Comment #7, bug #40322 (project make): Any news on this one? Should I close it? ___ Reply to this item at: http://savannah.gnu.org/bugs/?40322 ___ Message sent via/by Savannah

[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses

2013-11-29 Thread Mike Hommey
Follow-up Comment #8, bug #40322 (project make): Please close. I /think/ all the issues i've had so far are due to our intermediate processes not handling things well. I'll reopen if it turns out there is something wrong with make. ___

[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses

2013-11-29 Thread Eli Zaretskii
Update of bug #40322 (project make): Status:None = Not A Bug Open/Closed:Open = Closed ___ Reply to this item at:

[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses

2013-10-21 Thread Eli Zaretskii
Follow-up Comment #4, bug #40322 (project make): That is not what is supposed to happen. When you press Ctrl-C, the SIGINT handler is invoked, this is the function fatal_error_signal defined on command.c. (Please verify that the signal handler is indeed invoked.) Since on Windows SIGINT

[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses

2013-10-21 Thread Mike Hommey
Follow-up Comment #5, bug #40322 (project make): As a matter of fact, we do have an intermediate process for those commands. I'll double check what's actually happening. ___ Reply to this item at: http://savannah.gnu.org/bugs/?40322

[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses

2013-10-20 Thread Mike Hommey
URL: http://savannah.gnu.org/bugs/?40322 Summary: Interrupting a build with CTRL-C doesn't kill subprocesses Project: make Submitted by: glandium Submitted on: Mon 21 Oct 2013 12:28:18 AM GMT Severity: 3 - Normal

[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses

2013-10-20 Thread Eli Zaretskii
Follow-up Comment #1, bug #40322 (project make): This doesn't happen for me. Does it happen for you always, or just with some Makefile's? Can you show an example of a Makefile and a session where Ctrl-C does not interrupt the Make run? There's special code in Make to handle the Ctrl-C

[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses

2013-10-20 Thread Mike Hommey
Follow-up Comment #2, bug #40322 (project make): The typical case where this happens is when link.exe is running to link xul.dll in a Firefox build. I'll check at some other random places. I'll also check what happens with the commands.c code in a debugger.

[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses

2013-10-20 Thread Mike Hommey
Follow-up Comment #3, bug #40322 (project make): So it looks like from observing what happens, that subprocesses do get killed (although i haven't looked at what happens in a debugger), but they do so gently. Make doesn't wait for the process to actually be dead. Which has several interesting