#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):
I agree with all you say, but I think there's still a case for saying that
any stack trace is better than none. It may not be easily explicable to
Joe User, but it would give an expert a lot more to go on. It's a bit
like attaching a loudspeaker to the memory access pin of a CPU; you can't
explain the noises that come out, but you get to recognise them and they
can be very helpful. (Don't laugh -- I worked on an Eliot 803 which did
this! Well, I'm not sure which pin it was, but it made noises anyway.)
In short, I think there's a case for a quick-and-dirty stack trace, if
such a thing could be done without much effort.
Simon
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3693#comment:6>
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
