Open
Description
I inserted the following stack.yaml
into ghcjs-base and executed stack ghci
in ghcjs-base.
resolver: lts-6.20
compiler: ghcjs-0.2.0.9006020_ghc-7.10.3
compiler-check: match-exact
setup-info:
ghcjs:
source:
ghcjs-0.2.0.9006020_ghc-7.10.3:
url: http://ghcjs.tolysz.org/lts-6.20-9006020.tar.gz
sha1: a6cea90cd8121eee3afb201183c6e9bd6bacd94a
packages:
- '.'
extra-deps: []
flags: {}
extra-package-dbs: []
I had to push through multiple instances of segmentation faults to launch REPL on ghcjs-base. Does this issue still exist?
stack ghci
works fine on small toy GHCJS projects. Thus, I conjecture that it is related to nodejs memory limitations.
Metadata
Metadata
Assignees
Labels
No labels
Activity
crocket commentedon Oct 30, 2016
I found a good way to debug this issue.
I just needed to compile ghcjs with
--profile
or--enable-profiling
.+RTS -xc -RTS
will reveal the stack trace.crocket commentedon Oct 31, 2016
I can't compile stack and ghcjs-ghc7 with profiling.
ghcjs-ghc8 will probably be ok with profiling.
For stack, refer to commercialhaskell/stack#2751