[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses
From: |
Mike Hommey |
Subject: |
[bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses |
Date: |
Mon, 21 Oct 2013 00:28:19 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 |
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
Item Group: Bug
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Component Version: 4.0
Operating System: MS Windows
Fixed Release: None
Triage Status: None
_______________________________________________________
Details:
When interrupting a build with CTRL-C on a win32 build, whatever was run by
make at the time keeps running. This prevents subsequent make runs to run
properly, either because of file locking or because the still running commands
may alter the build directory during the second build.
Note this is not a problem new to 4.0, it happened with previous releases too,
as I am told.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?40322>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #40322] Interrupting a build with CTRL-C doesn't kill subprocesses,
Mike Hommey <=