cabal repl gets killed by interrupts

[ibotty]

i often use ctrl-c to reset the line i was in in ghci. unfortunately that kills cabal repl.

[23Skidoo]

/cc @dcoutts

[gracjan]

Note that cabal-dev ghci does not expose this problem.

[nmk]

Having the same problem with cabal repl. The exact error message is <stdin>: hGetChar: hardware fault (Input/output error).

[sol]

For me this is kind of a show stopper. Which is unfortunate, because I really want to use cabal sandbox + would love to get rid of all the custom .ghci files in my projects.

Why is this so important to me? If you develop long running process (web services, etc.), you may want to start them from ghci, modify some code, hit ctrl-c, do a :reload, start it again, ...

[dagit]

I think I've tracked this down to the way cabal spawns processes.

In cabal-dev the command that ultimately gets called to start ghci is System.Process.rawSystem. With cabal, I think, that it's using System.Process.runProcess.

Here is example code to show why I think this distinction matters:

import System.Process
import Control.Monad
import System.Exit

main = do
  exitcode <- rawSystem "ghci" []
  unless (exitcode == ExitSuccess) $ do
    exitFailure

  process <- runProcess "ghci" [] Nothing Nothing Nothing Nothing Nothing
  ec <- waitForProcess process
  unless (ec == ExitSuccess) $ do
    exitFailure

If you put that in a file and runhaskell on it, you will see that in the first ghci you can hit C-c as much as you want, but after you type :q and the second ghci starts up that hitting C-c will exit the process.

I tried to replace the call of runProcess in the Cabal sources to test out a bug fix (and hopefully send in a patch) but it's not working for me. Can someone who knows the Cabal sources try using rawSystem in the command that invokes ghci and test my theory? If it fixes the problem, then I think it indicates a bug in the process library.

[dagit]

By searching for runProcess in Distribution/Simple/Program/GHC.hs and doing a quick hack to replace them with calls to rawSystem I've now tested my theory. runProcess is to blame.

It looks like runProcess is used precisely so that an environment can be passed to the process, whereas rawSystem doesn't allow that.

Now, what should we do about it?

[wereHamster]

Which version of cabal includes this fix?

[23Skidoo]

@wereHamster Both HEAD and the 1.18 branch.

[gracjan]

Note: this strikes again.