[GHC] #3693: Show stack traces

[GHC]

#3693: Show stack traces
-------------------------------------+------------------------------------
        Reporter:  jpet              |            Owner:  Tarrasch
            Type:  feature request   |           Status:  new
        Priority:  normal            |        Milestone:  7.10.1
       Component:  Runtime System    |          Version:  6.10.4
      Resolution:                    |         Keywords:
Operating System:  Unknown/Multiple  |     Architecture:  Unknown/Multiple
 Type of failure:  None/Unknown      |       Difficulty:  Unknown
       Test Case:                    |       Blocked By:
        Blocking:                    |  Related Tickets:
-------------------------------------+------------------------------------

Comment (by simonmar):

 Simon - the best place to start is Peter and David's paper from last
 year's Haskell Symposium: http://dl.acm.org/citation.cfm?id=2503788

 I think the next level of detail is the comments in the code.  If you
 point to places where more explanation is needed, I'm sure Peter will be
 happy to add it.

 This is orthogonal to other methods for stack tracing, including the
 existing cost-centre-stack profiling.  What these patches do is establish
 a best-effort mapping from object code to source code, ''without affecting
 what code gets generated at all''.  It should have zero effect on
 optimisation - that's the main point.  Then we can use the information
 later to try to make sense of the stack, and for profiling.  There are
 follow-on patches to add support for these.

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