#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 simonpj):
Apart from update/exception frames, the stack mainly consists of frames
pushed by 'case'. If we put a string into each return-info-table (much as
we do already for constructors, I think), then we could record (a) module,
(b) top-level function (c) case binder... and that'd be plenty. It'd
bloat our binaries a bit but I'm betting it would not be much.
An alternative could be to do this only if you compile with -debug or
-ticky. But that would lose part of the benefit, I'm guessing.
Simon
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3693#comment:8>
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
