#3693: Show stack traces
------------------------------+---------------------------------------------
Reporter: jpet | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: _|_
Component: Runtime System | Version: 6.10.4
Resolution: | Keywords:
Difficulty: | Os: Unknown/Multiple
Testcase: | Architecture: Unknown/Multiple
Failure: None/Unknown |
------------------------------+---------------------------------------------
Comment (by asuffield):
For memory and disk space concerns, this is why we use .debug sections
(and sometimes place them in second files).
For the difficulty of accessing and dumping it, how about not duplicating
the effort? Emit the debugging information in DWARF format as if it was
any other language, and either borrow the code from gdb, or (perhaps
easier) teach gdb the few extra bits it needs to decipher ghc call stacks.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3693#comment:10>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
