#11317: Test prog003 fails with segfault on Windows (GHCi)
--------------------------------------+-------------------------------
Reporter: rdragon | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: GHCi | Version: 7.11
Keywords: | Operating System: Windows
Architecture: x86_64 (amd64) | Type of failure: GHCi crash
Test Case: | Blocked By:
Blocking: | Related Tickets: #11234
Differential Rev(s): | Wiki Page:
--------------------------------------+-------------------------------
On my `x86_64` Windows machine test `prog003` fails with a segfault:
{{{
cd ./ghci/prog003 && ghciWayFlags=-static HC="/home/Rik/ghc/inplace/bin
/ghc-stage2.exe" HC_OPTS="-dcore-lint -dcmm-lint -dno-debug-output -no-
user-package-db -rtsopts -fno-warn-tabs -fno-warn-missed-specialisations
-fno-ghci-history " "/home/Rik/ghc/inplace/bin/ghc-stage2.exe" -dcore-lint
-dcmm-lint -dno-debug-output -no-user-package-db -rtsopts -fno-warn-tabs
-fno-warn-missed-specialisations -fno-ghci-history --interactive -v0
-ignore-dot-ghci +RTS -I0.1 -RTS prog003.run.stdout
2> prog003.run.stderr >> prog003.run.stdout 2>> prog003.run.stderr
Wrong exit code (expected 0 , actual 1 )
Stdout:
Run 1
a :: Int -> Int
168
Run 2
(A.a,B.b,C.c,D.d)
:: (Float -> Float, Float -> Float, Float -> Float, Float -> Float)
28.0
Run 3
(A.a,B.b,C.c,D.d)
:: (Float -> Float, Float -> Float, Float -> Float, Float -> Float)
28.0
Run 4
(A.a,B.b,C.c,D.d)
:: (Float -> Float, Float -> Float, Float -> Float, Float -> Float)
28.0
Run 5
(A.a,B.b,C.c,D.d)
:: (Float -> Float, Float -> Float, Float -> Float, Float -> Float)
28.0
Run 6
(A.a,B.b,C.c,D.d)
:: (Float -> Float, Float -> Float, Float -> Float, Float -> Float)
28.0
Run 7
(A.a,B.b,C.c,D.d)
:: (Float -> Float, Float -> Float, Float -> Float, Float -> Float)
28.0
Run 8
Segmentation fault/access violation in generated code
Stderr:
*** unexpected failure for prog003(ghci)
}}}
(I do not think it is an access violation error since when I remove
[https://github.com/ghc/ghc/blob/c2fab84239299176a8e72aa26ae894019d677bd9/tes...
line 65] and everything below line 70, the same stdout is generated.)
This looks related to ticket #11234.
The GHC version used was
[http://git.haskell.org/ghc.git/commit/df6cb57b32d94b7f6f7c9a86207adfeee9712e...
df6cb57b32d94b7f6f7c9a86207adfeee9712ed6], although I already noticed the
problem with a version a few days older.
If someone could point me to information about how to install GDB suitable
for debugging GHC on my Windows machine I will try to post the stack
trace.
--
Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/11317
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler
