64-bit windows cabal.exe segfaults in GC
|Reported by:||awson||Owned by:|
|Operating System:||Windows||Architecture:||x86_64 (amd64)|
|Type of failure:||Runtime crash||Test Case:|
|Related Tickets:||Differential Rev(s):|
cabal.exe built with 64-bit windows GHC segfaults doing cabal configure or cabal install or probably something else.
This occurs *both* for cabal-install 184.108.40.206 built against Cabal 220.127.116.11 and for cabal-install 18.104.22.168 built against Cabal 22.214.171.124.
This occurs only for 64-bit build, 32-bit build is fine.
64-bit GHC-7.6.3 build is also fine.
During debugging I see segfault occurs inside evacuate somewhere near get_itbl call I guess.
If I make cabal.exe to not trigger some presumably bad GC compiling it with -rtsopts and running it as (for example) cabal +RTS -H256m -m50 -RTS ... the problem disappears.
Change History (96)
comment:4 Changed 2 years ago by awson
- Status changed from new to patch
comment:5 Changed 2 years ago by awson
- Component changed from None to Compiler
- Type of failure changed from None/Unknown to Runtime crash
comment:15 in reply to: ↑ 14 Changed 2 years ago by awson
comment:37 in reply to: ↑ 36 Changed 2 years ago by awson
comment:56 follow-up: ↓ 57 Changed 2 years ago by simonpj
comment:66 Changed 2 years ago by thoughtpolice
- Owner jstolarek deleted
- Status changed from patch to new
comment:68 Changed 2 years ago by thoughtpolice
- Milestone changed from 7.8.1 to 7.8.2
- Priority changed from highest to high
Changed 2 years ago by simonmar
comment:70 Changed 2 years ago by simonmar
- Milestone changed from 7.8.2 to 7.8.1
- Priority changed from high to highest
comment:80 Changed 2 years ago by thoughtpolice
comment:83 Changed 2 years ago by thoughtpolice
- Resolution set to fixed
- Status changed from new to closed