How to properly execute debug function for haskell-idea-plugin

I have installed haskell-idea-plugin to build Haskell IDE.

The plugin can do the following at https://github.com/Atsky/haskell-idea-plugin .

  • Haskell syntax syntax
  • Cabal syntax highlighting
  • Checking errors with ghc-modi.
  • Simple completion based on ghc-modi
  • Show Character Type (Ctrl + Shift + T or ⌘ + Shift + T on Mac)
  • Build cabal projects
  • Installation of cabin packages

  • REPL

But when I tried to debug the following simple Haskell file

module Main where

main = do
    str <- getLine
    putStrLn $ str++str

      

reported: Debug execution error: Internal error occured while executing debug process for untitled

And here is my Haskell-debugger config: enter image description here

I tried other options as well, but it didn't work.

And here is my environment:

  • Ubuntu14.10
  • oracle jdk6.0
  • IntelliJ IDEA 13.1.16
  • Haskell-idea-plugin
  • Ghc mod
  • remote-debugger
+3


source to share


1 answer


While I'm under windows, I got a similar error. Steps that worked for me to resolve the error:



  • Try running ghc-modi.exe

    from the command line. These were the times when this resulted in an error ghc-modi.exe: C:\Users\Nick\AppData\Roaming\cabal\bin\ghc-mod: createProcess: does not exist (No such file or directory)

    This is fixed by recompiling and installing ghc-mod

    from sources , I think ghc-modi

    contains a hard path to ghc-mod

    , and the compiled files cannot be moved across different machines.
  • Seems to remote-debugger

    have the same hard dependency on file system position. During one of my previous installations, I copied it from another machine and got it C:\Portable\ghc-7.10.1\lib\settings: openFile: does not exist (No such file or directory)

    . The fix is, again, rebuild remote-debugger

    from sources on the current computer.
  • Of course, all of these executables must be available in PATH

    .
  • After that, I created the project hello

    from scratch and (remote) debugging worked fine.
+2


source







All Articles