Wed Sep 5 03:47:16 PDT 2007 Simon Marlow <[EMAIL PROTECTED]>
* FIX #1650: ".boot modules interact badly with the ghci debugger"
In fact hs-boot files had nothing to do with it: the problem was that
GHCi would forget the breakpoint information for a module that had
been reloaded but not recompiled. It's amazing that we never noticed
this before.
The ModBreaks were in the ModDetails, which was the wrong place. When
we avoid recompiling a module, ModDetails is regenerated from ModIface
by typecheckIface, and at that point it has no idea what the ModBreaks
should be, so typecheckIface made it empty. The right place for the
ModBreaks to go is with the Linkable, which is retained when
compilation is avoided. So now I've placed the ModBreaks in with the
CompiledByteCode, which also makes it clear that only byte-code
modules have breakpoints.
This fixes break022/break023
M ./compiler/iface/TcIface.lhs -1
M ./compiler/main/DriverPipeline.hs -2 +2
M ./compiler/main/GHC.hs -1 +1
M ./compiler/main/HscMain.lhs -9 +9
M ./compiler/main/HscTypes.lhs -8 +7
M ./compiler/main/InteractiveEval.hs -5 +15
M ./compiler/main/TidyPgm.lhs -3 +2
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
