Given that the haddock.exe executable itself is crashing, it seems highly
unlikely to be a bug in either Stack or Cabal. I can think of three
possibilities here:
* There's a bug in Haddock itself, such as an FFI call or some embedded C
code
* There's a bug in GHC which is generating invalid code
* The GHC bindist itself has included a corrupted haddock.exe
I agree with Vanessa: trying to reproduce this with another build tool
(`cabal haddock` or `cabal new-haddock`) would be a good next step,
followed by a bug report against (most likely) GHC.
On Thu, Jul 19, 2018 at 9:29 AM Yuji Yamamoto
I always get an " Access violation in generated code when reading 0x28900000" error when executing
stack haddock haskell-src-exts
since LTS 12.0.
I'm not sure to which project I should submit a bug report. GHC? Haddock? Or Stack? And how can I make a smaller case to reproduce the same error?
I attached a log when executing with --verbose --cabal-verbose for your info.
-- 山本悠滋 twitter: @igrep GitHub: https://github.com/igrep GitLab: https://gitlab.com/igrep Facebook: http://www.facebook.com/igrep Google+: https://plus.google.com/u/0/+YujiYamamoto_igrep _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.