Thank you Michael and Vanessa! Here're what I've tried and their results: A. `cabal new-haddock` in a project depending on haskell-src-exts as you suggested. Resulted in another, non-related error..: > cabal new-haddock --with-ghc='C:\Users\yuji-yamamoto\AppData\Local\Programs\stack\x86_64-windows\ghc-8.4.3\bin\ghc.exe' Resolving dependencies... Build profile: -w ghc-8.4.3 -O1 In order, the following will be built (use -v for more details): - happy-1.19.9 (exe:happy) (requires build) - haskell-src-exts-1.20.2 (lib) (requires build) - proceedings-bot-0.1.0.0 (lib) (first run) Configuring happy-1.19.9 (all, legacy fallback)... cabal.exe: Failed to build happy-1.19.9 (which is required by proceedings-bot-0.1.0.0). The failure occurred during the configure step. The exception was: output of C:\Users\yuji-yamamoto\AppData\Local\Programs\stack\x86_64-windows\ghc-8.4.3\bin\ghc.exe: hGetContents: invalid argument (invalid byte sequence) B. Running a command extracted a log from `stack haddock --verbose haskell-src-exts`. Resulted in the same error

C:\sr\setup-exe-cache\x86_64-windows\Cabal-simple_Z6RU0evB_2.2.0.1_ghc-8.4.3.exe --builddir=.stack-work\dist\7d103d30 haddock --html --hoogle --haddock-option=--hyperlinked-source --verbose ... Access violation in generated code when reading 0x36f00000

Attempting to reconstruct a stack trace... Frame Code address * 0x440daf0 0xe63d37 C:\Users\yuji-yamamoto\AppData\Local\Programs\stack\x86_64-windows\ghc-8.4.3\bin\haddock.exe+0xa63d37 * 0x440daf8 0x7e1100049f40 C:\Users\yuji-yamamoto\p\cmder_mini\vendor\conemu-maximus5\ConEmu\ConEmuHk64.dll+0x49f40 C. Plus I found `stack haddock` after `stack unpack haskell-src-exts-1.20.2 && cd haskell-src-exts-1.20.2 Sounds weird... I'm happy if getting some more advice to make smaller case. Thanks, 2018年7月19日(木) 22:35 Michael Snoyman :

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 wrote:

...

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.

-- 山本悠滋 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

Thank you very much! I confirmed the replaced haddock executable can successfully generate the docs! 2018年7月21日(土) 4:42 Shao Cheng :

Hi Yamamoto-san,

I've encountered the same problem before, and there's a haddock issue tracking this problem: https://github.com/haskell/haddock/issues/837. A simple fix is building latest version of haddock and replacing the haddock binary for ghc-8.4.3.

On Fri, Jul 20, 2018 at 4:29 PM, Yuji Yamamoto < whosekiteneverfly@gmail.com> wrote:

...

Thank you Michael and Vanessa!

Here're what I've tried and their results:

A. `cabal new-haddock` in a project depending on haskell-src-exts as you suggested. Resulted in another, non-related error..: > cabal new-haddock --with-ghc='C:\Users\yuji-yamamoto\AppData\Local\Programs\stack\x86_64-windows\ghc-8.4.3\bin\ghc.exe' Resolving dependencies... Build profile: -w ghc-8.4.3 -O1 In order, the following will be built (use -v for more details): - happy-1.19.9 (exe:happy) (requires build) - haskell-src-exts-1.20.2 (lib) (requires build) - proceedings-bot-0.1.0.0 (lib) (first run) Configuring happy-1.19.9 (all, legacy fallback)... cabal.exe: Failed to build happy-1.19.9 (which is required by proceedings-bot-0.1.0.0). The failure occurred during the configure step. The exception was: output of

C:\Users\yuji-yamamoto\AppData\Local\Programs\stack\x86_64-windows\ghc-8.4.3\bin\ghc.exe: hGetContents: invalid argument (invalid byte sequence)

B. Running a command extracted a log from `stack haddock --verbose haskell-src-exts`. Resulted in the same error

...

C:\sr\setup-exe-cache\x86_64-windows\Cabal-simple_Z6RU0evB_2.2.0.1_ghc-8.4.3.exe --builddir=.stack-work\dist\7d103d30 haddock --html --hoogle --haddock-option=--hyperlinked-source --verbose ... Access violation in generated code when reading 0x36f00000

Attempting to reconstruct a stack trace...

Frame Code address * 0x440daf0 0xe63d37 C:\Users\yuji-yamamoto\AppData\Local\Programs\stack\x86_64-windows\ghc-8.4.3\bin\haddock.exe+0xa63d37 * 0x440daf8 0x7e1100049f40 C:\Users\yuji-yamamoto\p\cmder_mini\vendor\conemu-maximus5\ConEmu\ConEmuHk64.dll+0x49f40

C. Plus I found `stack haddock` after `stack unpack haskell-src-exts-1.20.2 && cd haskell-src-exts-1.20.2 Sounds weird...

I'm happy if getting some more advice to make smaller case.

Thanks,

2018年7月19日(木) 22:35 Michael Snoyman :

...

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 < whosekiteneverfly@gmail.com> wrote:

...

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.

-- 山本悠滋 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.

-- 山本悠滋 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

Hi, How does confirm that this bug is being hit. `stack haddock haskell-src-exts` on LTS-12.1 fails with the following cryptic error: -- While building custom Setup.hs for package haskell-src-exts-1.20.2 using: /home/vl/.stack/setup-exe-cache/x86_64-linux/Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.3 --builddir=.stack-work/dist/x86_64-linux/Cabal-2.2.0.1 haddock --html --hoogle --html-location=../$pkg-$version/ --haddock-option=--hyperlinked-source Process exited with code: ExitFailure (-11) Logs have been written to: /home/vl/vacationlabs/haskell/.stack-work/logs/haskell-src-exts-1.20.2.log The log file doesn't contain an error. How does one upgrade the haddock version and get stack to use it? -- Saurabh. On Mon, Jul 23, 2018 at 11:58 AM Sven Panne wrote:

Am Mo., 23. Juli 2018 um 05:49 Uhr schrieb Yuji Yamamoto < whosekiteneverfly@gmail.com>:

...

Thank you very much!

I confirmed the replaced haddock executable can successfully generate the docs!

Yesterday I had quite some trouble because of the Haddock problem, too, and I guess I'm not alone: haskell-src-exts has 165 direct reverse dependencies, so probably hundreds of Hackage packages are affected by this. The workaround is simple (don't use --haddock with stack), but far from satisfying and not very obvious.

Given the fact that this affects a very central piece of the Haskell infrastructure in its latest stable incarnation (GHC 8.4.3): Can we have an 8.4.4 with a fixed Haddock? _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

-- http://www.saurabhnanda.com

Hi cafe, Is there anyone on this list that can explain how to replace the haddock executable to solve the problem below? I replaced some haddock binary (which I build adding haddock-api-2.20.0 to my global stack config and doing stack install haddock), and I now have: $ ~/.stack/programs/x86_64-linux/ghc-8.4.3/bin/haddock --version Haddock version 2.20.0, (c) Simon Marlow 2006 Ported to use the GHC API by David Waern 2006-2008 This seems to be the latest Haddock release (and I am using Stack 1.7.1 which is also the latest), but my `stack haddock` build still results the same error as below (ExitFailure (-11)). Jeroen Bransen Op 26-7-2018 om 16:53 schreef Saurabh Nanda:

Hi,

How does confirm that this bug is being hit. `stack haddock haskell-src-exts` on LTS-12.1 fails with the following cryptic error:

    --  While building custom Setup.hs for package haskell-src-exts-1.20.2 using: /home/vl/.stack/setup-exe-cache/x86_64-linux/Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.3 --builddir=.stack-work/dist/x86_64-linux/Cabal-2.2.0.1 haddock --html --hoogle --html-location=../$pkg-$version/ --haddock-option=--hyperlinked-source     Process exited with code: ExitFailure (-11)     Logs have been written to: /home/vl/vacationlabs/haskell/.stack-work/logs/haskell-src-exts-1.20.2.log

The log file doesn't contain an error.

How does one upgrade the haddock version and get stack to use it?

-- Saurabh.

On Mon, Jul 23, 2018 at 11:58 AM Sven Panne mailto:svenpanne@gmail.com> wrote:

Am Mo., 23. Juli 2018 um 05:49 Uhr schrieb Yuji Yamamoto mailto:whosekiteneverfly@gmail.com>:

Thank you very much!

I confirmed the replaced haddock executable can successfully generate the docs!

Yesterday I had quite some trouble because of the Haddock problem, too, and I guess I'm not alone: haskell-src-exts has 165 direct reverse dependencies, so probably hundreds of Hackage packages are affected by this. The workaround is simple (don't use --haddock with stack), but far from satisfying and not very obvious.

Given the fact that this affects a very central piece of the Haskell infrastructure in its latest stable incarnation (GHC 8.4.3): Can we have an 8.4.4 with a fixed Haddock? _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org mailto:ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

-- http://www.saurabhnanda.com

_______________________________________________ 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.

Good suggestion, but unfortunately it is one that I replaced which is already version 2.20.0 Op 23-8-2018 om 10:35 schreef Yuji Yamamoto:

Try  `stack exec which haddock` to see in which directory your haddock is installed.

2018年8月23日(木) 17:32 Jeroen Bransen mailto:jeroen@chordify.net>:

Hi cafe,

Is there anyone on this list that can explain how to replace the haddock executable to solve the problem below? I replaced some haddock binary (which I build adding haddock-api-2.20.0 to my global stack config and doing stack install haddock), and I now have:

$ ~/.stack/programs/x86_64-linux/ghc-8.4.3/bin/haddock --version Haddock version 2.20.0, (c) Simon Marlow 2006 Ported to use the GHC API by David Waern 2006-2008

This seems to be the latest Haddock release (and I am using Stack 1.7.1 which is also the latest), but my `stack haddock` build still results the same error as below (ExitFailure (-11)).

Jeroen Bransen

Op 26-7-2018 om 16:53 schreef Saurabh Nanda:

...

Hi,

How does confirm that this bug is being hit. `stack haddock haskell-src-exts` on LTS-12.1 fails with the following cryptic error:

    --  While building custom Setup.hs for package haskell-src-exts-1.20.2 using: /home/vl/.stack/setup-exe-cache/x86_64-linux/Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.3 --builddir=.stack-work/dist/x86_64-linux/Cabal-2.2.0.1 haddock --html --hoogle --html-location=../$pkg-$version/ --haddock-option=--hyperlinked-source     Process exited with code: ExitFailure (-11)     Logs have been written to: /home/vl/vacationlabs/haskell/.stack-work/logs/haskell-src-exts-1.20.2.log

The log file doesn't contain an error.

How does one upgrade the haddock version and get stack to use it?

-- Saurabh.

On Mon, Jul 23, 2018 at 11:58 AM Sven Panne mailto:svenpanne@gmail.com> wrote:

Am Mo., 23. Juli 2018 um 05:49 Uhr schrieb Yuji Yamamoto mailto:whosekiteneverfly@gmail.com>:

Thank you very much!

I confirmed the replaced haddock executable can successfully generate the docs!

Yesterday I had quite some trouble because of the Haddock problem, too, and I guess I'm not alone: haskell-src-exts has 165 direct reverse dependencies, so probably hundreds of Hackage packages are affected by this. The workaround is simple (don't use --haddock with stack), but far from satisfying and not very obvious.

Given the fact that this affects a very central piece of the Haskell infrastructure in its latest stable incarnation (GHC 8.4.3): Can we have an 8.4.4 with a fixed Haddock? _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org mailto:ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

-- http://www.saurabhnanda.com

_______________________________________________ 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.

_______________________________________________ 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.

-- 山本悠滋 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