austin at well-typed.com
Thu Apr 3 14:00:08 UTC 2014
Kyrill, you are fantastic! I confirmed this incantation seems to have
fixed the problem on my build:
$ peflags --stack-reserve=0x200000 --stack-commit=0x200000 ghc.exe
with the RC2 build, and not my own. Hooray!
I will work up something soon. Thanks so much again!
On Thu, Apr 3, 2014 at 8:50 AM, Austin Seipp <austin at well-typed.com> wrote:
> Oh excellent, thank you for the tip Kyrill, I had no idea about this!
> My build is on the way, so I will try this and report back soon.
> On Thu, Apr 3, 2014 at 8:34 AM, kyra <kyrab at mail.ru> wrote:
>> On 4/3/2014 17:15, Austin Seipp wrote:
>>> Right now, Kyrill has suggested a fix I'm attempting (I slightly
>>> botched my first try), and I have found a way to avoid it at the
>>> moment by turning off optimization (which seems to reduce stack
>>> pressure enough to get by on Windows - see the ticket for details).
>> It's absolutely not necessary to rebuild everything to check if this works,
>> it's enough to edit ghc.exe with peflags utility (which has --stack-reserve
>> and --stack-commit options) and look if it stop segfaulting. If I could
>> reproduce the problem I'd have done this long ago.
>> ghc-devs mailing list
>> ghc-devs at haskell.org
> Austin Seipp, Haskell Consultant
> Well-Typed LLP, http://www.well-typed.com/
Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
More information about the ghc-devs