ninja-build/ninja

Signal handling does not work as expected

Open

#1 241 ouverte le 16 févr. 2017

Voir sur GitHub
 (2 commentaires) (0 réactions) (0 assignés)C++ (1 544 forks)batch import
help wanted

Métriques du dépôt

Stars
 (10 194 stars)
Métriques de merge PR
 (Merge moyen 39j 3h) (10 PRs mergées en 30 j)

Description

Ninja on POSIX systems currently puts children in their own process group. This policy causes a variety of problems, since ninja doesn't perfectly forward signals to children --- for example, C-z in the terminal sends a SIGTSTP (and then SIGSTOP) to ninja, but since ninja doesn't do anything special for SIGTSTP, the compilation jobs keep running. SIGINT frequently doesn't interrupt compilation jobs either.

In GNU Make, all of these interactions work as you'd expect.

Why do we need to put subprocesses in their own process group? This whole issue disappears if we don't put children in their own process groups, let them inherit the controlling terminal, and allow signal propagation to work normally.

Guide contributeur