Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

With GHC 7.8.1-RC2 I get scavenge_stack: weird activation record found on stack on "cabal install -j" #1716

Closed
adinapoli opened this issue Mar 9, 2014 · 1 comment

Comments

@adinapoli
Copy link

Hello everyone,

sorry if this was reported somewhere else, or if the GHC issue tracker would have been more appropriate.
I know that the dreadful "scavenge_stack" is nothing new, but it's the first time I see it on Mac OS X (I'm on Maverick, OS X 10.9.2).

This is a "stacktrace" of the problem. It seems to happen almost consistently if I try to do a parallel installation:

[hsenv]☁  ~HSENV  cabal install -j snap
Resolving dependencies...
Configuring HUnit-1.2.5.2...
Downloading MonadRandom-0.1.13...
Downloading logict-0.6.0.2...
cabal: internal error: scavenge_stack: weird activation record found on stack: 415597384
    (GHC version 7.8.0.20140228 for x86_64_apple_darwin)
    Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug
[1]    2328 abort      cabal install -j snap
[hsenv]☁  ~HSENV

The concerning thing is that it doesn't seem to be deterministic. After issuing that command, I have tried again and it worked this time:

[hsenv]☁  ~HSENV  cabal install -j snap
Resolving dependencies...
Configuring HUnit-1.2.5.2...
Downloading MonadRandom-0.1.13...
Configuring SHA-1.6.4...
Downloading logict-0.6.0.2...
Downloading process-1.1.0.2...
[...]

It seems to happen with every package and I have tried to install snap just for the sake of reproducing it.

Thanks!

Alfredo

ps. Cross posted on GHC HQ as well: https://ghc.haskell.org/trac/ghc/ticket/8866#ticket

@23Skidoo
Copy link
Member

23Skidoo commented Mar 9, 2014

Well, since this is a GHC bug, I don't think there's anything we can do on the Cabal side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants