stack Doesn't Work (that's what picture tell)

[cnd]

win 10 x64
C:\Users\Rainbow>stack --version
Version 1.1.0, Git revision 0e9430aad55841b5ff2c6c2851f0548c16bce7cf (3540 commits) x86_64 hpack-0.13.0

Access Violation

[mgsloan]

Wow, that's a rare thing indeed, I wonder what could cause it.

[cnd]

@mgsloan try set stack to spin (resolve many deps packages) like crazy on windows, e.g. run some stress tests, maybe it's not that hard to reproduce and people just don't pay much attention to it, e.g. it works if I just run same second time so it's a glitch

[mgsloan]

Seems like it's happened before: #898

I'm guessing it's something specific to your setup as otherwise I think we'd hear about it more. It's certainly possible there's a rare probabilistic bug here.

[cnd]

I really doubt if it's related to setup, there was nothing specific. What do you think about my stress test suggestion in case this issue was already known/reported

[mgsloan]

Was stack installed via the binary installer? If instead installed via cabal-install, one possibility is that it picked a dependency version that has a bug which causes segfaults.

I would appreciate an automated repro based on stress testing in some reproducible environment (container / vm image).

[cnd]

@mgsloan stack was installed via the binary installer but sure there is still one possibility is that binary stack is using some dependency version that has a bug which causes segfaults, sure

[mgsloan]

Right, I'm just trying to figure out why only 2 windows users are reporting this.

[mgsloan]

I am closing this as need repro, as it seems to be a rare thing, and I cannot investigate without a repro.

Opening #2134 about stress testing

[mgsloan]

This may be caused by http://www.echonolan.net/posts/2016-05-10-a-debugging-horror-story.html

See also #1689