Closing handle from runInteractiveProcess causes myserious, uncatchable death.
|Reported by:||cjs||Owned by:|
|Type of failure:||Test Case:|
|Related Tickets:||Differential Revisions:|
Running the attached program on Windows works, because runInteractiveProcess fails. Under Linux and NetBSD, runIntractiveProcess returns (which it probably shouldn't--wouldn't it be nicer if it checked that it had execute access on what it wanted to exec before it forked?) and then at some point in hClose the program silently dies, though returning an error code to the process that spawned it.