#2638: runInteractiveCommand on Win32 leaks, produces inconsistent behavior
-------------------------------+--------------------------------------------
Reporter: sclv | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: libraries/process | Version: 6.8.3
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Architecture: vax
Os: Windows |
-------------------------------+--------------------------------------------
Changes (by simonmar):
* difficulty: => Unknown
Comment:
What happens in the "noread" case is that `runInteractiveCommand` spawns a
shell to run "./rcTest noread", and then you terminate the shell by
calling `terminateProcess`. Windows doesn't have the concept of process
groups, so it doesn't kill the child process. I think this is behaving
correctly. If you want to be able to kill the child reliably, I suggest
using `runInteractiveProcess`, or the new `createProcess` (in 6.10)
instead.
I'm looking into the memory leak now.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2638#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
