Opened 3 years ago

Closed 2 years ago

#5565 closed bug (duplicate)

ghc reports a bug after interrupt

Reported by: kop Owned by:
Priority: normal Milestone:
Component: GHCi Version: 7.0.3
Keywords: Interrupt Cc:
Operating System: Windows Architecture: x86
Type of failure: GHCi crash Difficulty:
Test Case: Blocked By:
Blocking: Related Tickets:

Description (last modified by igloo)

Two or three times clicking Ctrl+C causes GHCI to type this:

ghc.exe: panic! (the 'impossible' happened)
  (GHC version 7.0.3 for i386-unknown-mingw32):
        thread blocked indefinitely in an MVar operation

Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

Attachments (3)

Session.txt (3.0 KB) - added by kop 3 years ago.
Full session and contents of loaded file
session-2.txt (8.3 KB) - added by porges 2 years ago.
my ghci session
session-2-part2 (4.9 KB) - added by porges 2 years ago.
managed to reproduce a third time (this log starts directly after previous one)

Download all attachments as: .zip

Change History (9)

Changed 3 years ago by kop

Full session and contents of loaded file

comment:1 Changed 3 years ago by igloo

  • Description modified (diff)

comment:2 Changed 3 years ago by igloo

Thanks for the report. So just to check: You didn't background ghci (e.g. press ^Z) at any point, right?

comment:3 Changed 2 years ago by porges

  • Architecture changed from x86 to Unknown/Multiple

I just got this (Windows 7, x64). No backgrounding. I managed to reproduce it once but not sure how.

I will attach a GHCi session log.

Changed 2 years ago by porges

my ghci session

comment:4 Changed 2 years ago by porges

  • Architecture changed from Unknown/Multiple to x86

Changed 2 years ago by porges

managed to reproduce a third time (this log starts directly after previous one)

comment:5 Changed 2 years ago by porges

Note that that last one was not after interrupt.

I tried to recreate the conditions under which it happened the second time, then starting writing up this bug report. Went back to the window and then mistyped ':r'.

comment:6 Changed 2 years ago by simonmar

  • Resolution set to duplicate
  • Status changed from new to closed

I think this is probably the same as #4245, although it is provoked by backgrounding on OS X. Hopefully it is the same underlying bug.

Note: See TracTickets for help on using tickets.