Behaviour of readProcess, and code simplicity (or lack thereof)

[Akio Takano]

Hi,


On Sat, Nov 16, 2013 at 6:59 AM, Duncan Coutts <duncan.coutts at googlemail.com
> wrote:

> Hi possibly-interested souls,
>
> In this patch to System.Process.readProcess from last year:
>
>
> https://ghc.haskell.org/trac/ghc/changeset/b5ee908863882d18e4110d96b43ccc1bb5068ceb/process
>
> Bas changed things so that if an async exception is received by the
> thread calling readProcess (or readProcessWithExitCode) then the
> external process gets forcibly terminated. I do mean forcibly, it's
> TerminateProcess() on Windows and SIGKILL (not SIGTERM) on Unix.
>

The documentation says 'terminateProcess sends the process the SIGTERM
signal'. Also it seems to agree with the implementation
(cbits/runProcess.c:321).

Takano Akio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20131121/9b826443/attachment.html>