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

Akio Takano tkn.akio at
Thu Nov 21 08:52:58 UTC 2013


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

> Hi possibly-interested souls,
> In this patch to System.Process.readProcess from last year:
> 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

Takano Akio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ghc-devs mailing list