Ticket #828 (closed bug: fixed)

Opened 7 years ago

Last modified 4 years ago

ghc -e 'Control.Monad.Fix.mfix error' panics

Reported by: duncan Owned by:
Priority: low Milestone:
Component: GHCi Version: 6.5
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: Difficulty: Easy (less than 1 hour)
Test Case: Blocked By:
Blocking: Related Tickets:

Description

Just for the record, a low priority bug...

Folk on IRC found this obscure torture test:

Control.Monad.Fix.mfix error

Depending on how you run it it gives different errors.

Compiling a module main = mfix error works fine:

ghc foo.hs -o foo
./foo
foo: <<loop>>

It exits with a non-zero exit code as expected.

ghci fares a little worse but ok:

Prelude> Control.Monad.Fix.mfix error
*** Exception: *** Exception: <<loop>>

So actually the only way that goes wrong is ghc -e :

ghc -e 'Control.Monad.Fix.mfix error'
*** Exception: ghc-6.4.2: panic! (the `impossible' happened, GHC version 6.4.2):
        <<loop>>

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

Same behaviour with recent ghc-6.5.

So I'd guess it's just the catching of errors in ghc -e that's not quite right, probably because of the way that tring to generate the error message generates an error.

Change History

Changed 7 years ago by Lemmih

  • difficulty changed from Unknown to Easy (1 hr)
  • os changed from Linux to Multiple
  • component changed from Driver to GHCi
  • architecture changed from x86_64 (amd64) to Multiple

Changed 7 years ago by Lemmih

  • status changed from new to closed
  • resolution set to fixed

Changed 5 years ago by simonmar

  • architecture changed from Multiple to Unknown/Multiple

Changed 5 years ago by simonmar

  • os changed from Multiple to Unknown/Multiple

Changed 4 years ago by simonmar

  • difficulty changed from Easy (1 hr) to Easy (less than 1 hour)
Note: See TracTickets for help on using tickets.