-
Notifications
You must be signed in to change notification settings - Fork 20
ghc-mod interactive command info failed with error ghc-modi crashed #83
Comments
This same thing hit me today (also windows 10). Steps to repro: |
So, technically speaking, this is a problem with ghc-mod that we fixed in 5.5.0.0 (not yet released). In particular, paths with spaces don't always work. That said, I could probably do something about it. |
1.5.4 should help somewhat. |
Hi, |
@Softsapiens, please post full error log. To do that, click that small clipboard icon right of 'report/view issue' button, then paste clipboard contents here. Thanks. |
ok... going for it |
[Enter steps to reproduce below:]
Atom Version: 1.3.2 Stack TraceHaskell-ghc-mod: ghc-mod interactive command info failed with error ghc-modi crashed
Commands
Config{
"core": {
"ignoredNames": [
".git",
".svn",
".DS_Store"
],
"disabledPackages": [
"cabal",
"cabal",
"cabal",
"cabal",
"cabal",
"cabal",
"cabal",
"cabal",
"vim-mode",
"term2"
],
"themes": [
"one-light-ui",
"one-light-syntax"
]
},
"haskell-ghc-mod": {
"ghcModPath": "/Users/dani/.cabal/bin/ghc-mod",
"ghcModiPath": "/Users/dani/.cabal/bin/ghc-modi",
"debug": true
}
} Installed Packages# User
Ensime, v0.31.1
aligner-php, v1.0.0
atom-dart, v0.7.2
autocomplete-haskell, v0.6.2
autocomplete-php, v0.3.7
emmet, v2.3.17
file-icons, v1.6.13
flex-tool-bar, v0.7.3
git-log, v0.4.1
haskell-ghc-mod, v1.5.4
haskell-pointfree, v0.1.3
hyperclick, v0.0.35
ide-haskell, v1.3.9
jshint, v1.8.3
language-elm, v1.3.1
language-haskell, v1.5.2
language-idris, v0.4.0
language-purescript, v0.6.1
language-scala, v1.1.4
language-swift, v0.4.0
linter, v1.11.3
minimap, v4.19.0
project-manager, v2.7.1
tool-bar, v0.1.10
tool-bar-main, v0.0.8
tree-view-finder, v0.2.1
# Dev
No dev packages |
@Softsapiens, this is a different issue. Please read https://github.com/atom-haskell/haskell-ghc-mod#configuration, especially the last paragraph. |
yes, I see your point. During the tests I started atom in different ways... usually I open it from terminal, but this last time I made it from the dock. Now I set the additionalPathDirectories... Ok, It's not working... but now the package don't crush. With ghc-modi disabled, I see this log in the console: haskell-ghc-mod debug: getProcessOptions(/Users/dani/Code/haskell/servant-example) And with ghc-modi enabled, the log is: haskell-ghc-mod debug: getProcessOptions(/Users/dani/Code/haskell/servant-example) |
Basically what you need to take from this is:
This usually indicates a problem with ghc packages, a misconfigured cabal project, or traces of builds with other GHC versions... somewhere Things to try:
|
I'm using stack. Globally I've installed ghc 7.10.3, but this project uses locally ghc 7.10.2... slack manages it |
Oh. Okay. Then forget everything I said, I have no idea how stack works. That said, try running Atom with |
I'd just like to note that I've upgraded to ghc-mod-5.5.0.0 and have had no issues so far, i.e. this no longer happens to me. |
@LukaHorvat thanks for confirming. |
It's not working, but now the problem seems to be related with: |
@Softsapiens, frankly I can't help much with stack. All I know it sometimes works. And other times, it doesn't. I see no pattern and I don't use it personally, at least not at the moment. Primary problem with stack seems to be basically this: DanielG/ghc-mod#615. Also environment, but that's mostly solved by |
Totally agree. I think, that's a big problem... because stack is extremely powerful and useful. I wish it gets working. Thanks a lot for your help and time! |
I get it working now... installing a local ghc-mod via stack in the project, and starting atom through stack exec... no additionalPathDirectories used, stack manages all the paths, as you commented before. thanks again |
I get this error randomly when working on a file. Here's the log
Atom Version: 1.3.2
System: Microsoft Windows 10 Education
Thrown From: haskell-ghc-mod package, v1.5.3
Stack Trace
Haskell-ghc-mod: ghc-mod interactive command info failed with error ghc-modi crashed
Commands
Config
Installed Packages
The text was updated successfully, but these errors were encountered: