[GHC] #10656: Ability to get stack traces from Haskell code

[GHC]

#10656: Ability to get stack traces from Haskell code
-------------------------------------+-------------------------------------
        Reporter:  bgamari           |                   Owner:  Tarrasch
            Type:  feature request   |                  Status:  new
        Priority:  normal            |               Milestone:  7.12.1
       Component:  Compiler          |                 Version:  7.10.1
      Resolution:                    |                Keywords:
Operating System:  Unknown/Multiple  |            Architecture:
 Type of failure:  None/Unknown      |  Unknown/Multiple
      Blocked By:                    |               Test Case:
 Related Tickets:  #3693             |                Blocking:
                                     |  Differential Revisions:  Phab:D963
-------------------------------------+-------------------------------------
Description changed by bgamari:

Old description:

> With the merge of Phab:D169 and Phab:D396 (included in GHC 7.10.1) GHC
> now has the ability to produce DWARF debugging information in compiled
> binaries.
>
> It would be nice if Haskell programs could request stack backtraces from
> the RTS. Tarrasch has some work in this direction in Phab:D963 however
> there are a number of questions that remain outstanding,
>
>  * do we want to rely on an external library for parsing DWARF
> information? If so, how do we address portability concerns?
>
>  * What should the Haskell-land interfaces look like? Writing down some
> concrete use-cases would help here.

New description:

 With the merge of Phab:D169 and Phab:D396 (included in GHC 7.10.1, see
 #3693 for details) GHC now has the ability to produce DWARF debugging
 information in compiled binaries.

 It would be nice if Haskell programs could request stack backtraces from
 the RTS. Tarrasch has some work in this direction in Phab:D963 however
 there are a number of questions that remain outstanding,

  * do we want to rely on an external library for parsing DWARF
 information? If so, how do we address portability concerns?

  * What should the Haskell-land interfaces look like? Writing down some
 concrete use-cases would help here.

--

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