Breakpoint code instrumentation
authorPepe Iborra <mnislaih@gmail.com>
Sun, 10 Dec 2006 20:49:34 +0000 (20:49 +0000)
committerPepe Iborra <mnislaih@gmail.com>
Sun, 10 Dec 2006 20:49:34 +0000 (20:49 +0000)
commit376101055fb111ebd52b5ef1fb76e00334b44304
tree97a1d1293298b77760e0523bbbe772181c29cbbc
parent3a99fa889bdff0c86df20cb18c71d30e30a79b43
Breakpoint code instrumentation

Instrumentation gets activated by the '-fdebugging' dynflag.

All the instrumentation occurrs in the desugarer; it consists of inserting 'breakpoint' combinators at a number of places in the AST, namely:
 - Binding sites
 - Do-notation statements
These 'breakpoint' combinators will later be further desugared (at DsExpr) into ___Jump functions.
For more info about this and all the ghci.debugger see the page at the GHC wiki:

http://hackage.haskell.org/trac/ghc/wiki/GhciDebugger
13 files changed:
compiler/deSugar/Desugar.lhs
compiler/deSugar/DsBreakpoint.lhs
compiler/deSugar/DsExpr.lhs
compiler/deSugar/DsGRHSs.lhs
compiler/deSugar/DsMonad.lhs
compiler/iface/TcIface.lhs
compiler/main/Breakpoints.hs
compiler/main/DynFlags.hs
compiler/main/GHC.hs
compiler/main/HscMain.lhs
compiler/main/HscTypes.lhs
compiler/main/TidyPgm.lhs
compiler/typecheck/TcRnDriver.lhs