Ticket #2810 (closed feature request: duplicate)

Opened 4 years ago

Last modified 4 years ago

Debugger: change context to the module containing the current breakpoint

Reported by: simonmar Owned by:
Priority: normal Milestone: 6.12 branch
Component: GHCi Version: 6.8.3
Keywords: Cc: phercek@…
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: Difficulty: Moderate (less than a day)
Test Case: Blocked By:
Blocking: Related Tickets:

Description

Moved part of #2740 here.

When we stop at a breakpoint, perhaps we should change the current context (:module) to the module that contains the breakpoint location. That would at least give access to a similar scope to that in which the breakpoint expression is located.

Change History

Changed 4 years ago by phercek

  • cc phercek@… added

I was asked by mnislaih to create separate ticket for what looks exactly like this. If you did not mean something special then this is the same as the earlier created ticket #2803

Changed 4 years ago by simonmar

  • status changed from new to closed
  • resolution set to duplicate

closing as dup of #2803

Changed 4 years ago by simonmar

  • difficulty changed from Moderate (1 day) to Moderate (less than a day)
Note: See TracTickets for help on using tickets.