[GHC] #11047: Provide call stacks in GHCi

[GHC]

#11047: Provide call stacks in GHCi
-------------------------------------+-------------------------------------
        Reporter:  simonmar          |                Owner:  simonmar
            Type:  task              |               Status:  new
        Priority:  high              |            Milestone:  8.0.1
       Component:  GHCi              |              Version:  7.11
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  None/Unknown      |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:  #545, #4837       |  Differential Rev(s):  Phab:D1407
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by gridaphobe):

 Just for clarity, could you elaborate on how this differs from the
 existing call stacks that you can print in ghci? Is the main difference
 that currently ghci's call stack only traces byte-compiled code?

 It's also not clear to me how we're going to avoid exposing the details of
 lazy evaluation. Both the breakpoint-based traces and the SCC-based traces
 currently expose lazy evaluation (which I agree is a bad thing, at least
 for error debugging!). I guess this means extending the byte-code
 interpreter to distinguish between a lexical call-site vs entering a
 closure based on demand?

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/11047#comment:4>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler