#2945: trace history should be global or add command :mergetrace
------------------------------+---------------------------------------------
Reporter: phercek | Owner:
Type: feature request | Status: new
Priority: normal | Milestone:
Component: GHCi | Version: 6.10.1
Severity: normal | Resolution:
Keywords: debugger | Testcase:
Os: Unknown/Multiple | Architecture: Unknown/Multiple
------------------------------+---------------------------------------------
Changes (by phercek):
* summary: trace history should not be context/resume specific but
global => trace history should be global or add
command :mergetrace
Comment:
Nobody responded on the mailing list but I realized that there may be a
use case for trace history being context/resume specific. An user may
suspect some fuction is buggy and may want to inspect its behavior with
different input values while stopped at a breakpoint. This would polute
the global history since some of the function inputs would be different
from the ones used in the debugged instance. An alternative to the global
history is to store off the trace history of the last nested resume
context after it finished and provide a command :mergetrace which would
merge the last finished trace to the current trace. This does not change
anything in the current user interface (it just adds one more command) so
it should be acceptable for everybody.
I do not mind which way it is finaly resolved. I just want access to the
trace which just finished. From my point of view, whatever is easier to do
is fine.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2945#comment:2>
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
