Ticket #1057 (new bug)

Opened 5 years ago

Last modified 3 years ago

Implicit parameters on breakpoints

Reported by: mnislaih Owned by:
Priority: normal Milestone: _|_
Component: GHCi Version: 6.8.2
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: Difficulty: Moderate (less than a day)
Test Case: ghci.debugger/break015 Blocked By:
Blocking: Related Tickets:

Description

Bring implicit parameters into the examine scope in breakpoints.

Test case is ghci.debugger break004

Change History

Changed 5 years ago by mnislaih

  • owner set to mnislaih
  • status changed from new to assigned

Changed 4 years ago by igloo

What's the status of this bug?

break004 isn't run by ghci.debugger/scripts/all.T, and it doesn't use implicit parameters, so I'm a bit confused.

Changed 4 years ago by mnislaih

  • owner mnislaih deleted
  • status changed from assigned to new
  • version changed from 6.6 to 6.8.2
  • testcase changed from ghci.debugger/break004 to ghci.debugger/break015

The defect still exists and the test is break015.

I am not going to fix it, as a lot has changed since I did the 1st prototype implementation. I don't know exactly how the debugger captures locals currently, the code was written by Simon and Bernie, and I don't feel comfortable fixing this ticket on myself.

Changed 4 years ago by igloo

  • milestone changed from 6.8 branch to 6.10 branch

Changed 4 years ago by simonmar

  • architecture changed from Unknown to Unknown/Multiple

Changed 4 years ago by simonmar

  • os changed from Unknown to Unknown/Multiple

Changed 3 years ago by igloo

  • milestone changed from 6.10 branch to _|_

Changed 3 years ago by simonmar

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