Hello! I have been bisecting this issue but in order to be successful, I need a simple reproducer which isn't trivial since I cannot just reuse the build directory of an unsuccessful build due to the changing Haskell libraries for different GHC versions.
Ideally, we should have a single command line with GHC which will trigger the segmentation fault. To bisect, I have done the following: # git bisect start # git bisect good ghc-8.10.7-release # git bisect bad ghc-9.2.7-release # git submodule update --init # ./boot ; python3 boot # echo "SRC_HC_OPTS += -lffi -latomic -optl-pthread" >> mk/build.mk && \ echo "Stage1Only := YES" >> mk/build.mk && \ echo 'utils/genprimopcode_CONFIGURE_OPTS += "-f-build-tool-depends"' \ >> mk/build.mk && echo 'compiler_CONFIGURE_OPTS += "-f-build-tool-depends"' \ >> mk/build.mk && echo 'utils/hpc_CONFIGURE_OPTS += "-f-build-tool-depends"' \ >> mk/build.mk && echo "HADDOCK_DOCS := NO" >> mk/build.mk \ && echo "BUILD_SPHINX_HTML := NO" >> mk/build.mk && echo "BUILD_SPHINX_PDF := NO" \ >> mk/build.mk # ./configure && make -j32 For newer versions, the build has to be performed with Hadrian, so the last step would be: # ./hadrian/build -j Prior to using Hadrian for the first time, the package database needs to be updated: # cabal update Now, if I had a simple reproducer, it would be rather easy to bisect the issue. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
