runhaskell crash with .hi/.o files in the directory

[guest]

I've been playing around with the ICFP "universal machine" puzzle ( http://icfpcontest.org/task.shtml) For prototyping, I'm using runhaskell as a "script engine" from the SciTE editor on Win32. I'm running Windows XP Home 2002 SP2 with the package GHC6.6 downloaded from haskell.org.

I have some leftover .o/.hi files from compiling a previous version the project via the command line. If I delete those, the problem goes away.

I'll attach a zip of the directory contents as a repro case if the bug tracker allows me to.

>runhaskell um.hs
trying to Allocate array of size 0..
trying to Abandon size 0 allocation..
trying to Allocate size 11..
trying Array Index on allocated array..
trying Amendment of allocated array..
checking Amendment of allocated array..
trying Alloc(a,a) and amending it..
comparing multiple allocations..
pointer arithmetic..
check old allocation..
simple tests ok!
um.hs: internal error: interpretBCO: unknown or unimplemented opcode 22656
    (GHC version 6.6 for i386_unknown_mingw32)
    Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
>Exit code: 3

[guest]

Repro case

[guest]

More info: - If I delete unit.o, utils.o or unit.hi, the crash goes away - If I delete utils.hi, I get the following error message:

runhaskell um.hs

<interactive>: Unit.o: unknown symbol `_Utils_z3fU_closure'

Exit code: 1

Note that I haven't changed either of those .hs files since I last compiled them, and, in fact, the code doesn't reference anything defined in either of them except the import statement.

[simonmar]

Possibly the same as #1013.

Is it possible to reproduce the bug from scratch?

[simonmar]

No answer from submitter; I tried the example code and couldn't reproduce any bugs. The "unknown or unimplemented opcode" crash is almost certainly the same as #1013, and the other problems are most likely due to inconsistent .o/.hi files.